aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJens Axboe <[email protected]>2025-08-21 19:24:57 +0000
committerJens Axboe <[email protected]>2025-08-21 19:54:01 +0000
commite4e6aaea46b7be818eba0510ba68d30df8689ea3 (patch)
tree2347c2cd0c784d5e28ff901fa737a739fdbce4e3
parentio_uring/futex: ensure io_futex_wait() cleans up properly on failure (diff)
downloadkernel-e4e6aaea46b7be818eba0510ba68d30df8689ea3.tar.gz
kernel-e4e6aaea46b7be818eba0510ba68d30df8689ea3.zip
io_uring: clear ->async_data as part of normal init
Opcode handlers like POLL_ADD will use ->async_data as the pointer for double poll handling, which is a bit different than the usual case where it's strictly gated by the REQ_F_ASYNC_DATA flag. Be a bit more proactive in handling ->async_data, and clear it to NULL as part of regular init. Init is touching that cacheline anyway, so might as well clear it. Signed-off-by: Jens Axboe <[email protected]>
-rw-r--r--io_uring/io_uring.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index 4ef69dd58734..93633613a165 100644
--- a/io_uring/io_uring.c
+++ b/io_uring/io_uring.c
@@ -2119,6 +2119,7 @@ static int io_init_req(struct io_ring_ctx *ctx, struct io_kiocb *req,
req->file = NULL;
req->tctx = current->io_uring;
req->cancel_seq_set = false;
+ req->async_data = NULL;
if (unlikely(opcode >= IORING_OP_LAST)) {
req->opcode = 0;