qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>,
	eblake@redhat.com, Hanna Czenczek <hreitz@redhat.com>,
	qemu-block@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Fam Zheng <fam@euphon.net>,
	hibriansong@gmail.com
Subject: [PATCH v6 03/15] aio-posix: fix spurious return from ->wait() due to signals
Date: Mon,  3 Nov 2025 21:29:21 -0500	[thread overview]
Message-ID: <20251104022933.618123-4-stefanha@redhat.com> (raw)
In-Reply-To: <20251104022933.618123-1-stefanha@redhat.com>

io_uring_enter(2) only returns -EINTR in some cases when interrupted by
a signal. Therefore the while loop in fdmon_io_uring_wait() is
incomplete and can lead to a spurious early return.

Handle the case when a signal interrupts io_uring_enter(2) but the
syscall returns the number of SQEs submitted (that takes priority over
-EINTR).

This patch probably makes little difference for QEMU, but the test suite
relies on the exact pattern of aio_poll() return values, so it's best to
hide this io_uring syscall interface quirk.

Here is the strace of test-aio receiving 3 SIGCONT signals after this
fix has been applied. Notice how the io_uring_enter(2) return value is 1
the first time because an SQE was submitted, but -EINTR the other times:

  eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 9
  io_uring_enter(7, 1, 0, 0, NULL, 8) = 1
  clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, 0x7ffe38a46240) = 0
  io_uring_enter(7, 1, 1, IORING_ENTER_GETEVENTS, NULL, 8) = 1
  --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=596096, si_uid=1000} ---
  io_uring_enter(7, 0, 1, IORING_ENTER_GETEVENTS, NULL, 8) = -1 EINTR (Interrupted system call)
  --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=596096, si_uid=1000} ---
  io_uring_enter(7, 0, 1, IORING_ENTER_GETEVENTS, NULL, 8 <unfinished ...>
  <... io_uring_enter resumed>) = -1 EINTR (Interrupted system call)
  --- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=596096, si_uid=1000} ---
  io_uring_enter(7, 0, 1, IORING_ENTER_GETEVENTS, NULL, 8 <unfinished ...>
  <... io_uring_enter resumed>) = 0

Reported-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 util/fdmon-io_uring.c | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/util/fdmon-io_uring.c b/util/fdmon-io_uring.c
index b64ce42513..3d8638b0e5 100644
--- a/util/fdmon-io_uring.c
+++ b/util/fdmon-io_uring.c
@@ -299,9 +299,16 @@ static int fdmon_io_uring_wait(AioContext *ctx, AioHandlerList *ready_list,
 
     fill_sq_ring(ctx);
 
+    /*
+     * Loop to handle signals in both cases:
+     * 1. If no SQEs were submitted, then -EINTR is returned.
+     * 2. If SQEs were submitted then the number of SQEs submitted is returned
+     *    rather than -EINTR.
+     */
     do {
         ret = io_uring_submit_and_wait(&ctx->fdmon_io_uring, wait_nr);
-    } while (ret == -EINTR);
+    } while (ret == -EINTR ||
+             (ret >= 0 && wait_nr > io_uring_cq_ready(&ctx->fdmon_io_uring)));
 
     assert(ret >= 0);
 
-- 
2.51.1



  parent reply	other threads:[~2025-11-04  2:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04  2:29 [PATCH v6 00/15] aio: add the aio_add_sqe() io_uring API Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 01/15] aio-posix: fix race between io_uring CQE and AioHandler deletion Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 02/15] aio-posix: fix fdmon-io_uring.c timeout stack variable lifetime Stefan Hajnoczi
2025-11-04  2:29 ` Stefan Hajnoczi [this message]
2025-11-04  2:29 ` [PATCH v6 04/15] aio-posix: keep polling enabled with fdmon-io_uring.c Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 05/15] tests/unit: skip test-nested-aio-poll with io_uring Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 06/15] aio-posix: integrate fdmon into glib event loop Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 07/15] aio: remove aio_context_use_g_source() Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 08/15] aio: free AioContext when aio_context_new() fails Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 09/15] aio: add errp argument to aio_context_setup() Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 10/15] aio-posix: gracefully handle io_uring_queue_init() failure Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 11/15] aio-posix: unindent fdmon_io_uring_destroy() Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 12/15] aio-posix: add fdmon_ops->dispatch() Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 13/15] aio-posix: add aio_add_sqe() API for user-defined io_uring requests Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 14/15] block/io_uring: use aio_add_sqe() Stefan Hajnoczi
2025-11-04  2:29 ` [PATCH v6 15/15] block/io_uring: use non-vectored read/write when possible Stefan Hajnoczi
2025-11-04 10:38 ` [PATCH v6 00/15] aio: add the aio_add_sqe() io_uring API Kevin Wolf
2025-11-13  8:27 ` Michael Tokarev
2025-11-13 13:32   ` Kevin Wolf
2025-11-13 14:51     ` Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251104022933.618123-4-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=eblake@redhat.com \
    --cc=fam@euphon.net \
    --cc=hibriansong@gmail.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).