This is the mail archive of the
mailing list for the Cygwin project.
Re: Postgres Backend doesn't catch the next command, after SIGUSR2
- From: Patrick Samson <p_samson at yahoo dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 30 Mar 2004 01:03:00 -0800 (PST)
- Subject: Re: Postgres Backend doesn't catch the next command, after SIGUSR2
--- Corinna Vinschen wrote:
> When WSAWaitForMultipleEvents returns
> WSA_WAIT_EVENT_0 + 1, you can be
> sure that the event hasn't happen at this point.
> Otherwise it would
> have returned WSA_WAIT_EVENT_0. Unfortunately this
> doesn't mean that
> the event couldn't happen a nanosecond later.
> If the signal has arrived and the WSARecvFrom call
> should be interrupted,
> you can't just go ahead, since the call to
> WSARecvFrom got a pointer
> to application allocated memory. You can't rely on
> the fact that the
> application will keep this memory intact after
> recvfrom returned with
> EINTR. If you do, Windows might scramble
> application memory. To avoid
> that, the CancelIo cancels the active call.
> Having said that, does the below change at least
> alleviates the problem?
> The implementation would have to be changed a bit
> more to get this
> entirely non-racy, though.
> Index: net.cc
> RCS file: /cvs/src/src/winsup/cygwin/net.cc,v
> retrieving revision 1.162
> diff -u -p -r1.162 net.cc
> --- net.cc 29 Mar 2004 14:08:44 -0000 1.162
> +++ net.cc 29 Mar 2004 14:09:17 -0000
> @@ -83,7 +83,9 @@ wsock_event::wait (int socket,
> LPDWORD f
> ret = (int) len;
> case WSA_WAIT_EVENT_0 + 1:
> - if (!CancelIo ((HANDLE) socket))
> + if (WSAGetOverlappedResult (socket, &ovr, &len,
> FALSE, flags))
> + ret = (int) len;
> + else if (!CancelIo ((HANDLE) socket))
> debug_printf ("CancelIo() %E, fallback to
> blocking io");
> WSAGetOverlappedResult (socket, &ovr, &len,
> TRUE, flags);
Probably Yes, but even reduced, there is still room
between WSAGetOverlappedResult and CancelIo to loose
What about first cancel the I/O op and then look
for possible data?
"All I/O operations that are canceled will complete
with the error ERROR_OPERATION_ABORTED. All completion
notifications for the I/O operations will occur
What's your feeling about:
if (!CancelIo ((HANDLE) socket))
if (WSAGetOverlappedResult (socket, &ovr, &len,
FALSE, flags) && len != 0)
ret = (int) len;
else WSASetLastError (WSAEINTR);
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html