Re: [PATCH] Cygwin: select: don't report read ready on a FIFO never, opened for writing

2022-10-19 Thread Ken Brown
On 10/18/2022 11:45 AM, Corinna Vinschen wrote: On Sep 23 11:31, Ken Brown wrote: @@ -1043,6 +1043,8 @@ writer_shmem: set_pipe_non_blocking (get_handle (), flags & O_NONBLOCK); nwriters_lock (); inc_nwriters (); + if (!writer_opened () ) +set_writer_opened (); My personal pref

Re: [PATCH] Cygwin: select: don't report read ready on a FIFO never, opened for writing

2022-10-18 Thread Corinna Vinschen
On Sep 23 11:31, Ken Brown wrote: > Patch attached. I'm also attaching a test case, that behaves the same on > Cygwin as on Linux. Interesting case, but thinking about the scenario, it seems logical to do it this way. > @@ -1043,6 +1043,8 @@ writer_shmem: >set_pipe_non_blocking (get_handle (

[PATCH] Cygwin: select: don't report read ready on a FIFO never, opened for writing

2022-09-23 Thread Ken Brown
l); } From f4a92734eac17dbfc7ff3541eef9611c87184ed0 Mon Sep 17 00:00:00 2001 From: Ken Brown Date: Fri, 23 Sep 2022 10:24:04 -0400 Subject: [PATCH] Cygwin: select: don't report read ready on a FIFO never opened for writing According to POSIX and the Linux man page, select(2) is supposed