)]}' { "commit": "636b836d5f4e36ceebb788e2e0d4724f7f9406e1", "tree": "93944141541d10969d8d4aba91068785271d2692", "parents": [ "8bac3ba57eecc466b7e73dabf7d19328a59f684e" ], "author": { "name": "Stefan Hajnoczi", "email": "stefanha@redhat.com", "time": "Wed Apr 08 10:11:39 2020 +0100" }, "committer": { "name": "Stefan Hajnoczi", "email": "stefanha@redhat.com", "time": "Thu Apr 09 15:55:06 2020 +0100" }, "message": "aio-posix: signal-proof fdmon-io_uring\n\nThe io_uring_enter(2) syscall returns with errno\u003dEINTR when interrupted\nby a signal. Retry the syscall in this case.\n\nIt\u0027s essential to do this in the io_uring_submit_and_wait() case. My\ninterpretation of the Linux v5.5 io_uring_enter(2) code is that it\nshouldn\u0027t affect the io_uring_submit() case, but there is no guarantee\nthis will always be the case. Let\u0027s check for -EINTR around both APIs.\n\nNote that the liburing APIs have -errno return values.\n\nSigned-off-by: Stefan Hajnoczi \u003cstefanha@redhat.com\u003e\nReviewed-by: Stefano Garzarella \u003csgarzare@redhat.com\u003e\nReviewed-by: Philippe Mathieu-Daudé \u003cphilmd@redhat.com\u003e\nMessage-id: 20200408091139.273851-1-stefanha@redhat.com\nSigned-off-by: Stefan Hajnoczi \u003cstefanha@redhat.com\u003e\n", "tree_diff": [ { "type": "modify", "old_id": "b4d6109f20bdc9c2a35772b3d0e1123a2223c29f", "old_mode": 33188, "old_path": "util/fdmon-io_uring.c", "new_id": "d5a80ed6fbdebeaf7095526687705f3e8c153993", "new_mode": 33188, "new_path": "util/fdmon-io_uring.c" } ] }