public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: sten.kristian.ivarsson@gmail.com
Cc: 'cygwin' <cygwin@cygwin.com>
Subject: Re: Sv: Sv: Named pipes and multiple writers
Date: Fri, 27 Mar 2020 09:10:18 -0400	[thread overview]
Message-ID: <b311d907-7376-5bc6-3216-7d2b96728dbc@cornell.edu> (raw)
In-Reply-To: <ce4a4877-df77-3400-e8ac-16655b313757@cornell.edu>

[-- Attachment #1: Type: text/plain, Size: 775 bytes --]

On 3/26/2020 7:19 PM, Ken Brown via Cygwin wrote:
> On 3/26/2020 6:39 PM, Ken Brown via Cygwin wrote:
>> On 3/26/2020 6:01 PM, sten.kristian.ivarsson@gmail.com wrote:
>>> The ENIXIO occurs when parallel child-processes simultaneously using
>>> O_NONBLOCK opening the descriptor.
>>
>> This is consistent with my guess that the error is generated by 
>> fhandler_fifo::wait.  I have a feeling that read_ready should have been 
>> created as a manual-reset event, and that more care is needed to make sure 
>> it's set when it should be.
>>
>>> I could provide a code-snippet
>>> to reproduce it if wanted ?
>>
>> Yes, please!
> 
> That might not be necessary.  If you're able to build the git repo master 
> branch, please try the attached patch.

Here's a better patch.

Ken

[-- Attachment #2: 0001-Cygwin-FIFO-fix-a-problem-opening-nonblocking-writer.patch --]
[-- Type: text/plain, Size: 1828 bytes --]

From 3efd5a8cbff8d48b8cf9807070134bb79f591b7d Mon Sep 17 00:00:00 2001
From: Ken Brown <kbrown@cornell.edu>
Date: Thu, 26 Mar 2020 19:02:16 -0400
Subject: [PATCH] Cygwin: FIFO: fix a problem opening nonblocking writers

Make read_ready a manual-reset event.  Previously, when it was an
auto-reset event, there was a brief period when read_ready was not set
after a writer opened.  An attempt to open a second writer during this
period would fail with ENXIO if O_NONBLOCK was set, even if a reader
was open.

For the same reason, move ResetEvent(read_ready) from
listen_client_thread() to close().

Addresses: https://sourceware.org/pipermail/cygwin/2020-March/244201.html
---
 winsup/cygwin/fhandler_fifo.cc | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/winsup/cygwin/fhandler_fifo.cc b/winsup/cygwin/fhandler_fifo.cc
index 19cd0e507..c7e27e883 100644
--- a/winsup/cygwin/fhandler_fifo.cc
+++ b/winsup/cygwin/fhandler_fifo.cc
@@ -463,7 +463,6 @@ fhandler_fifo::listen_client_thread ()
 out:
   if (evt)
     CloseHandle (evt);
-  ResetEvent (read_ready);
   if (ret < 0)
     debug_printf ("exiting with error, %E");
   else
@@ -516,7 +515,7 @@ fhandler_fifo::open (int flags, mode_t)
 
   char npbuf[MAX_PATH];
   __small_sprintf (npbuf, "r-event.%08x.%016X", get_dev (), get_ino ());
-  if (!(read_ready = CreateEvent (sa_buf, false, false, npbuf)))
+  if (!(read_ready = CreateEvent (sa_buf, true, false, npbuf)))
     {
       debug_printf ("CreateEvent for %s failed, %E", npbuf);
       res = error_set_errno;
@@ -1016,6 +1015,8 @@ fhandler_fifo::close ()
      handler or another thread. */
   fifo_client_unlock ();
   int ret = stop_listen_client ();
+  if (reader && read_ready)
+    ResetEvent (read_ready);
   if (read_ready)
     CloseHandle (read_ready);
   if (write_ready)
-- 
2.21.0


  reply	other threads:[~2020-03-27 13:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 11:11 sten.kristian.ivarsson
2020-03-25 12:44 ` Ken Brown
     [not found]   ` <18be01d602ab$0bbfca30$233f5e90$@gmail.com>
2020-03-26 14:06     ` Sv: " Ken Brown
2020-03-26 15:11       ` Ken Brown
2020-03-26 16:03         ` Norton Allen
2020-03-26 16:44           ` Ken Brown
2020-03-26 17:00             ` Norton Allen
2020-03-26 22:01       ` Sv: " sten.kristian.ivarsson
2020-03-26 22:39         ` Ken Brown
2020-03-26 23:19           ` Ken Brown
2020-03-27 13:10             ` Ken Brown [this message]
2020-03-27 14:53               ` Sv: " sten.kristian.ivarsson
2020-03-27 22:56                 ` Ken Brown
2020-03-27 23:00                   ` Ken Brown
2020-03-28 12:10                   ` Sv: " sten.kristian.ivarsson
2020-03-28 15:43                     ` Ken Brown
2020-03-29  2:19                       ` Ken Brown
2020-03-30 17:44                         ` Ken Brown
2020-03-31 21:10                           ` Sv: " sten.kristian.ivarsson
2020-03-31 22:02                             ` Ken Brown
2020-04-01  7:45                               ` Sv: " sten.kristian.ivarsson
2020-04-01 13:47                                 ` Ken Brown
2020-04-01  8:52                               ` sten.kristian.ivarsson
2020-04-01 16:15                                 ` Ken Brown
2020-04-01 17:14                                   ` Sv: " sten.kristian.ivarsson
2020-04-01 18:34                                     ` Ken Brown
2020-04-02  2:19                                       ` Ken Brown
2020-04-02  8:05                                         ` Sv: " sten.kristian.ivarsson
2020-04-02 12:47                                           ` Sv: Sv: Sv: Sv: Sv: Sv: Sv: Sv: Named pipes and multiple wri Gregery Barton
2020-04-02 18:21                                           ` Sv: Sv: Sv: Sv: Sv: Sv: Sv: Sv: Named pipes and multiple writers Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b311d907-7376-5bc6-3216-7d2b96728dbc@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=sten.kristian.ivarsson@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).