[DragonFlyBSD - Bug #3307] select() not working as expect when a pipe is closed

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #3307 has been updated by deef.


And, AFAIR, in case the remote closes connection "properly", the descriptor should appear in readfds, and read()ing from it then returns zero. That's "the correct" way to detect connection closed by remote.

----------------------------------------
Bug #3307: select() not working as expect when a pipe is closed
http://bugs.dragonflybsd.org/issues/3307#change-14195

* Author: tmunro
* Status: New
* Priority: Normal
* Target version: 6.0
* Start date: 2021-11-19
----------------------------------------
When a the write end of a pipe is in the writefds set of a call to select(), and the read end is closed, I think select() should report the descriptor as writable (because writing would produce EPIPE or SIGPIPE), but it does not.  We suspect this changed, and we noticed the change in the PostgreSQL build farm after upgrading an ancient Dragonfly build machine to the current release.  In our real usage, this causes Perl IPC::Run in our test harness to hang, but here's a minimal repro in C:

https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BUZi3tp%3De0ffO1R7eZ%3Dx8azSJDNzO0E2zOy9PhuyOpAQ%40mail.gmail.com#f90edeec19759a8b62ce98ea5a11cb6e

(Please disregard the discussion of kqueue problems on ancient macOS, which turned out to be a separate problem, completely unrelated).



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account