From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Cc: [email protected]
Subject: Re: [PATCH 1/2] io_uring/uring_cmd: cleanup struct io_uring_cmd_data layout
Date: Thu, 23 Jan 2025 14:57:55 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 1/23/25 14:54, Jens Axboe wrote:
> On 1/23/25 7:38 AM, Pavel Begunkov wrote:
>> On 1/23/25 14:21, Jens Axboe wrote:
>>> A few spots in uring_cmd assume that the SQEs copied are always at the
>>> start of the structure, and hence mix req->async_data and the struct
>>> itself.
>>>
>>> Clean that up and use the proper indices.
>>>
>>> Signed-off-by: Jens Axboe <[email protected]>
>>> ---
>>> io_uring/uring_cmd.c | 6 +++---
>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/io_uring/uring_cmd.c b/io_uring/uring_cmd.c
>>> index 3993c9339ac7..6a63ec4b5445 100644
>>> --- a/io_uring/uring_cmd.c
>>> +++ b/io_uring/uring_cmd.c
>>> @@ -192,8 +192,8 @@ static int io_uring_cmd_prep_setup(struct io_kiocb *req,
>>> return 0;
>>> }
>>> - memcpy(req->async_data, sqe, uring_sqe_size(req->ctx));
>>> - ioucmd->sqe = req->async_data;
>>> + memcpy(cache->sqes, sqe, uring_sqe_size(req->ctx));
>>> + ioucmd->sqe = cache->sqes;
>>> return 0;
>>> }
>>> @@ -260,7 +260,7 @@ int io_uring_cmd(struct io_kiocb *req, unsigned int issue_flags)
>>> struct io_uring_cmd_data *cache = req->async_data;
>>> if (ioucmd->sqe != (void *) cache)
>>> - memcpy(cache, ioucmd->sqe, uring_sqe_size(req->ctx));
>>> + memcpy(cache->sqes, ioucmd->sqe, uring_sqe_size(req->ctx));
>>
>> 3347fa658a1b ("io_uring/cmd: add per-op data to struct io_uring_cmd_data")
>>
>> IIUC the patch above is queued for 6.14, and with that this patch
>> looks like a fix? At least it feels pretty dangerous without.
>
> It's not a fix, the sqes are first in the struct even with that patch.
Ah yes
> So I'd consider it a cleanup. In any case, targeting 6.14 for these
> alloc cache cleanups as it got introduced there as well.
That's good, makes it not that brittle
--
Pavel Begunkov
next prev parent reply other threads:[~2025-01-23 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 14:21 [PATCHSET 0/2] Cleanup alloc cache init_once handling Jens Axboe
2025-01-23 14:21 ` [PATCH 1/2] io_uring/uring_cmd: cleanup struct io_uring_cmd_data layout Jens Axboe
2025-01-23 14:38 ` Pavel Begunkov
2025-01-23 14:54 ` Jens Axboe
2025-01-23 14:57 ` Pavel Begunkov [this message]
2025-01-23 14:58 ` Jens Axboe
2025-01-23 14:21 ` [PATCH 2/2] io_uring: get rid of alloc cache init_once handling Jens Axboe
2025-01-23 14:27 ` Pavel Begunkov
2025-01-23 14:47 ` Pavel Begunkov
2025-01-23 14:55 ` Jens Axboe
2025-01-23 15:05 ` Pavel Begunkov
2025-01-23 15:09 ` Jens Axboe
2025-01-23 14:54 ` 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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