Re: [2/4] server: Add access mapping for a named pipe device object, adjust its default access rights. Resend.

[Dmitry Timoshkov]

Alexandre Julliard  wrote:
> > > Why do you need this for the device?
> >
> > Because of
> > ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so pipe.c && touch pipe.ok
> > pipe.c:109: Test failed: WaitNamedPipe failed (3)
> > pipe.c:116: Test failed: wrong error 3
> > pipe.c:109: Test failed: WaitNamedPipe failed (3)
> > pipe.c:116: Test failed: wrong error 3
> >
> > WaitNamedPipeW() opens a pipe device with FILE_READ_ATTRIBUTES.
>
> That doesn't mean it should use the same access as a named pipe object.

Yes, but currently it fails because default read access rights don't contain
FILE_READ_ATTRIBUTES, and while write access does specify FILE_CREATE_PIPE_INSTANCE
all access doesn't contain FILE_CREATE_PIPE_INSTANCE access.