Displaying 3 results from an estimated 3 matches for "nbd_aio_notify_err".
Did you mean:
nbd_aio_notify_error
2019 Jun 27
3
[libnbd PATCH 0/2] socket handling cleanups
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
2019 Jun 27
1
Re: [libnbd PATCH 2/2] poll: Improve our interface
...sed 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 write end, so read()
> will eventually see EOF even if we have to drain a buffer first).
>
> Perhaps we also want to add an nbd_aio_notify_err() that can inform
> the machine of any externally-detected error on the fd to the server,
> where the poll loop invokes that on POLLERR, and where we tweak the
> generator to permit that external event in any other public state.
> But that's a bigger patch.
> ---
> generator/...
2019 Jun 27
0
[libnbd PATCH 2/2] poll: Improve our interface
...andle 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 write end, so read()
will eventually see EOF even if we have to drain a buffer first).
Perhaps we also want to add an nbd_aio_notify_err() that can inform
the machine of any externally-detected error on the fd to the server,
where the poll loop invokes that on POLLERR, and where we tweak the
generator to permit that external event in any other public state.
But that's a bigger patch.
---
generator/generator | 18 +++++++++++++--...