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 02/15] aio-posix: fix fdmon-io_uring.c timeout stack variable lifetime
Date: Mon,  3 Nov 2025 21:29:20 -0500	[thread overview]
Message-ID: <20251104022933.618123-3-stefanha@redhat.com> (raw)
In-Reply-To: <20251104022933.618123-1-stefanha@redhat.com>

io_uring_prep_timeout() stashes a pointer to the timespec struct rather
than copying its fields. That means the struct must live until after the
SQE has been submitted by io_uring_enter(2). add_timeout_sqe() violates
this constraint because the SQE is not submitted within the function.

Inline add_timeout_sqe() into fdmon_io_uring_wait() so that the struct
lives at least as long as io_uring_enter(2).

This fixes random hangs (bogus timeout values) when the kernel loads
undefined timespec struct values from userspace after the original
struct on the stack has been destroyed.

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

diff --git a/util/fdmon-io_uring.c b/util/fdmon-io_uring.c
index ad89160f31..b64ce42513 100644
--- a/util/fdmon-io_uring.c
+++ b/util/fdmon-io_uring.c
@@ -188,20 +188,6 @@ static void add_poll_remove_sqe(AioContext *ctx, AioHandler *node)
     io_uring_sqe_set_data(sqe, NULL);
 }
 
-/* Add a timeout that self-cancels when another cqe becomes ready */
-static void add_timeout_sqe(AioContext *ctx, int64_t ns)
-{
-    struct io_uring_sqe *sqe;
-    struct __kernel_timespec ts = {
-        .tv_sec = ns / NANOSECONDS_PER_SECOND,
-        .tv_nsec = ns % NANOSECONDS_PER_SECOND,
-    };
-
-    sqe = get_sqe(ctx);
-    io_uring_prep_timeout(sqe, &ts, 1, 0);
-    io_uring_sqe_set_data(sqe, NULL);
-}
-
 /* Add sqes from ctx->submit_list for submission */
 static void fill_sq_ring(AioContext *ctx)
 {
@@ -291,13 +277,24 @@ static int process_cq_ring(AioContext *ctx, AioHandlerList *ready_list)
 static int fdmon_io_uring_wait(AioContext *ctx, AioHandlerList *ready_list,
                                int64_t timeout)
 {
+    struct __kernel_timespec ts;
     unsigned wait_nr = 1; /* block until at least one cqe is ready */
     int ret;
 
     if (timeout == 0) {
         wait_nr = 0; /* non-blocking */
     } else if (timeout > 0) {
-        add_timeout_sqe(ctx, timeout);
+        /* Add a timeout that self-cancels when another cqe becomes ready */
+        struct io_uring_sqe *sqe;
+
+        ts = (struct __kernel_timespec){
+            .tv_sec = timeout / NANOSECONDS_PER_SECOND,
+            .tv_nsec = timeout % NANOSECONDS_PER_SECOND,
+        };
+
+        sqe = get_sqe(ctx);
+        io_uring_prep_timeout(sqe, &ts, 1, 0);
+        io_uring_sqe_set_data(sqe, NULL);
     }
 
     fill_sq_ring(ctx);
-- 
2.51.1



  parent reply	other threads:[~2025-11-04  2:30 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 ` Stefan Hajnoczi [this message]
2025-11-04  2:29 ` [PATCH v6 03/15] aio-posix: fix spurious return from ->wait() due to signals Stefan Hajnoczi
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-3-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).