From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH 1/4] io_uring/uring_cmd: get rid of using req->imu
Date: Mon, 21 Oct 2024 20:59:31 -0600 [thread overview]
Message-ID: <f29d4778-b5f5-4f3c-a2e6-463c5432dd65@kernel.dk> (raw)
In-Reply-To: <ZxcRQZzAmwm1XT3K@fedora>
On 10/21/24 8:43 PM, Ming Lei wrote:
> On Mon, Oct 21, 2024 at 08:03:20PM -0600, Jens Axboe wrote:
>> It's pretty pointless to use io_kiocb as intermediate storage for this,
>> so split the validity check and the actual usage. The resource node is
>> assigned upfront at prep time, to prevent it from going away. The actual
>> import is never called with the ctx->uring_lock held, so grab it for
>> the import.
>>
>> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>> ---
>> io_uring/uring_cmd.c | 22 +++++++++++++++++-----
>> 1 file changed, 17 insertions(+), 5 deletions(-)
>>
>> diff --git a/io_uring/uring_cmd.c b/io_uring/uring_cmd.c
>> index 39c3c816ec78..313e2a389174 100644
>> --- a/io_uring/uring_cmd.c
>> +++ b/io_uring/uring_cmd.c
>> @@ -211,11 +211,15 @@ int io_uring_cmd_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)
>> struct io_ring_ctx *ctx = req->ctx;
>> u16 index;
>>
>> - req->buf_index = READ_ONCE(sqe->buf_index);
>> - if (unlikely(req->buf_index >= ctx->nr_user_bufs))
>> + index = READ_ONCE(sqe->buf_index);
>> + if (unlikely(index >= ctx->nr_user_bufs))
>> return -EFAULT;
>> - index = array_index_nospec(req->buf_index, ctx->nr_user_bufs);
>> - req->imu = ctx->user_bufs[index];
>> + req->buf_index = array_index_nospec(index, ctx->nr_user_bufs);
>> + /*
>> + * Pi node upfront, prior to io_uring_cmd_import_fixed()
>> + * being called. This prevents destruction of the mapped buffer
>> + * we'll need at actual import time.
>> + */
>> io_req_set_rsrc_node(req, ctx, 0);
>> }
>> ioucmd->cmd_op = READ_ONCE(sqe->cmd_op);
>> @@ -272,8 +276,16 @@ int io_uring_cmd_import_fixed(u64 ubuf, unsigned long len, int rw,
>> struct iov_iter *iter, void *ioucmd)
>> {
>> struct io_kiocb *req = cmd_to_io_kiocb(ioucmd);
>> + struct io_ring_ctx *ctx = req->ctx;
>> + struct io_mapped_ubuf *imu;
>> + int ret;
>>
>> - return io_import_fixed(rw, iter, req->imu, ubuf, len);
>> + mutex_lock(&ctx->uring_lock);
>> + imu = ctx->user_bufs[req->buf_index];
>> + ret = io_import_fixed(rw, iter, imu, ubuf, len);
>> + mutex_unlock(&ctx->uring_lock);
>
> io_uring_cmd_import_fixed is called in nvme ->issue(), and ->uring_lock
> may be held already.
Gah indeed, in fact it always should be, unless it's forcefully punted
to io-wq. I'll sort that out, thanks. And looks like we have zero tests
for uring_cmd + fixed buffers :-(
--
Jens Axboe
next prev parent reply other threads:[~2024-10-22 2:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 2:03 [PATCHSET v2 for-next 0/4] Get rid of io_kiocb->imu Jens Axboe
2024-10-22 2:03 ` [PATCH 1/4] io_uring/uring_cmd: get rid of using req->imu Jens Axboe
2024-10-22 2:43 ` Ming Lei
2024-10-22 2:59 ` Jens Axboe [this message]
2024-10-22 8:34 ` Anuj Gupta
2024-10-22 13:18 ` Jens Axboe
2024-10-22 13:24 ` Jens Axboe
2024-10-22 2:03 ` [PATCH 2/4] io_uring/rw: " Jens Axboe
2024-10-22 2:03 ` [PATCH 3/4] io_uring/net: move send zc fixed buffer import to issue path Jens Axboe
2024-10-22 2:03 ` [PATCH 4/4] io_uring: kill 'imu' from struct io_kiocb Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2024-10-22 13:32 [PATCHSET v3 for-next 0/4] Get rid of io_kiocb->imu Jens Axboe
2024-10-22 13:32 ` [PATCH 1/4] io_uring/uring_cmd: get rid of using req->imu Jens Axboe
2024-10-18 18:38 [PATCHSET for-next 0/4] Get rid of io_kiocb->imu Jens Axboe
2024-10-18 18:38 ` [PATCH 1/4] io_uring/uring_cmd: get rid of using req->imu Jens Axboe
2024-10-18 19:34 ` Pavel Begunkov
2024-10-19 21:56 ` Jens Axboe
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=f29d4778-b5f5-4f3c-a2e6-463c5432dd65@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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