search for: nbd_internal_pol

While working on a new test of what happens when the server goes away while commands are in flight, I managed to hit a race where I hit death from SIGPIPE instead of a clean transition to the DEAD state. I also found myself wanting to use nbd_poll from the test, but with a way to distinguish between the state machine progressing vs. hanging. Eric Blake (2): socket: Avoid SIGPIPE where possible

On 6/26/19 11:29 PM, Eric Blake wrote: > Make nbd_poll slightly more like poll(), allowing a user to detect > timeouts by returning 0 on timeout and 1 when we made progress. It > turns out that none of our internal uses ever expect a timeout (we > only call nbd_internal_poll with timeout==-1 because we expect a reply > from the server), but the public function might as well be nicer. > > Also handle POLLERR (server closed its read end, so our writes will > fail) and POLLNVAL (the fd itself is closed) as outright errors, and > POLLHUP the same as POLLIN...

Make nbd_poll slightly more like poll(), allowing a user to detect timeouts by returning 0 on timeout and 1 when we made progress. It turns out that none of our internal uses ever expect a timeout (we only call nbd_internal_poll with timeout==-1 because we expect a reply from the server), but the public function might as well be nicer. Also handle POLLERR (server closed its read end, so our writes will fail) and POLLNVAL (the fd itself is closed) as outright errors, and POLLHUP the same as POLLIN (the server closed its w...