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 <axboe@kernel.dk>

diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
index 4ef69dd58734aee28ed03a5d9c2be5dcedfb12ee..93633613a1657c0b6a618c688501e8e61336cc68 100644 (file)
--- 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;