[Bug 59126] New: NtFsControlFile(FSCTL_PIPE_WAIT) fails to detect infinite timeout

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59126

            Bug ID: 59126
           Summary: NtFsControlFile(FSCTL_PIPE_WAIT) fails to detect
                    infinite timeout
           Product: Wine
           Version: 10.20
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: ntdll
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

When calling NtFsControlFile with the FSCTL_PIPE_WAIT control code, the Timeout
field in the FILE_PIPE_WAIT_FOR_BUFFER structure is not interpreted correctly.
An infinite timeout (equivalent to NMPWAIT_WAIT_FOREVER in kernel32's
WaitNamedPipeW) is, on Windows proper, specified by the minimum signed 64-bit
integer value, i.e. 0x8000_0000_0000_0000. This behavior is not documented, but
can be observed by tracing the ntdll calls triggered by WaitNamedPipeW; and
ReactOS also agrees with this value.

However, Wine instead represents an infinite timeout using the value
0x7FFF_FFFF_FFFF_FFFF (the *maximum* signed 64-bit integer, aka
TIMEOUT_INFINITE). This logic is internally consistent: the WaitNamedPipeW
implementation converts NMPWAIT_WAIT_FOREVER to that value, and the server
detects it in async_set_timeout (called from named_pipe_device_ioctl in
server/named_pipe.c). However, it causes direct usage of this ntdll API to
incorrectly return STATUS_IO_TIMEOUT when the correct "infinite timeout" value
is passed.

I suspect the logic in named_pipe_device_ioctl should be modified to detect the
special value 0x8000_0000_0000_0000 and avoid setting a timeout in that case,
and that WaitNamedPipeW should be modified to translate NMPWAIT_WAIT_FOREVER to
that value rather than 0x7FFF_FFFF_FFFF_FFFF.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 59126] NtFsControlFile(FSCTL_PIPE_WAIT) fails to detect infinite timeout

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59126

--- Comment #1 from Alexandre Julliard <[e-mail]> ---
Is there any app that depends on this? Tracing the internal calls of Windows is
not allowed, and not something we want to replicate unless necessary.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.