diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2020-04-08 10:11:39 +0100 |
|---|---|---|
| committer | Stefan Hajnoczi <stefanha@redhat.com> | 2020-04-09 15:55:06 +0100 |
| commit | 636b836d5f4e36ceebb788e2e0d4724f7f9406e1 (patch) | |
| tree | 93944141541d10969d8d4aba91068785271d2692 /stubs/error-printf.c | |
| parent | 8bac3ba57eecc466b7e73dabf7d19328a59f684e (diff) | |
| download | qemu-636b836d5f4e36ceebb788e2e0d4724f7f9406e1.zip qemu-636b836d5f4e36ceebb788e2e0d4724f7f9406e1.tar.gz qemu-636b836d5f4e36ceebb788e2e0d4724f7f9406e1.tar.bz2 | |
aio-posix: signal-proof fdmon-io_uring
The io_uring_enter(2) syscall returns with errno=EINTR when interrupted
by a signal. Retry the syscall in this case.
It's essential to do this in the io_uring_submit_and_wait() case. My
interpretation of the Linux v5.5 io_uring_enter(2) code is that it
shouldn't affect the io_uring_submit() case, but there is no guarantee
this will always be the case. Let's check for -EINTR around both APIs.
Note that the liburing APIs have -errno return values.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-id: 20200408091139.273851-1-stefanha@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'stubs/error-printf.c')
0 files changed, 0 insertions, 0 deletions