Date: Thu, 17 Sep 2015 01:10:59 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203162] when close(fd) on a fifo fails with EINTR, the file descriptor is not really closed Message-ID: <bug-203162-8-CqRtc3QcF8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-203162-8@https.bugs.freebsd.org/bugzilla/> References: <bug-203162-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203162 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #4 from Konstantin Belousov <kib@FreeBSD.org> --- Created attachment 161136 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=161136&action=edit A bit more fairness into the signal interruption of fifo open The patch would prefer to return success over the EINTR when signal is delivered while other end of fifo becomes ready simultaneously. Note that the patch still does not fix the fundamental underground issue of the troubles, which is in the test structure itself. If child reader manages to close fifo before the parent writer sleeping in open has a chance to run, parent would deadlock, since nothing else would open the fifo for read. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-203162-8-CqRtc3QcF8>