From: Jens Axboe <axboe@kernel.dk>
To: Caleb Sander Mateos <csander@purestorage.com>,
Yang Xiuwei <yangxiuwei@kylinos.cn>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH 1/2] io_uring/uring_cmd: copy SQE before issue_blocking punt
Date: Thu, 2 Jul 2026 14:15:04 -0600 [thread overview]
Message-ID: <ce98e216-98bf-42cf-b1a0-89a2ea62f897@kernel.dk> (raw)
In-Reply-To: <CADUfDZp4DmCvwGyp9dJEEojSbkkcW8Bj9ZZEXVg3vw_7KsWhyQ@mail.gmail.com>
On 7/2/26 12:06 PM, Caleb Sander Mateos wrote:
> On Thu, Jul 2, 2026 at 10:43 AM Caleb Sander Mateos
> <csander@purestorage.com> wrote:
>>
>> On Thu, Jul 2, 2026 at 1:41 AM Yang Xiuwei <yangxiuwei@kylinos.cn> wrote:
>>>
>>> io_uring_cmd_issue_blocking() punts to io-wq without copying the SQE
>>> off the submission queue, unlike the -EAGAIN and fallback paths. Copy
>>> the SQE into async data before queuing the work.
>>
>> Add a Fixes tag?
>> Fixes: ecf47d452ced ("io_uring/uring_cmd: implement ->sqe_copy() to
>> avoid unnecessary copies")
>
> Actually I'm not convinced this is an issue at all. Since commit
> 212ec34e4e72 ("block: only read from sqe on initial invocation of
> blkdev_uring_cmd()"), blkdev_uring_cmd() only accesses the SQE on the
> initial issue. Even if the uring_cmd is re-issued asynchronously, it
> doesn't rely on the SQE having been preserved.
Yeah I agree, after taking a closer look. I'll kill this patch. I do
like your followup cleaning up the punting, will queue that for 7.3.
--
Jens Axboe
next prev parent reply other threads:[~2026-07-02 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 8:29 [PATCH 0/2] io_uring/uring_cmd cleanups Yang Xiuwei
2026-07-02 8:29 ` [PATCH 1/2] io_uring/uring_cmd: copy SQE before issue_blocking punt Yang Xiuwei
2026-07-02 17:43 ` Caleb Sander Mateos
2026-07-02 18:06 ` Caleb Sander Mateos
2026-07-02 20:15 ` Jens Axboe [this message]
2026-07-02 8:29 ` [PATCH 2/2] io_uring/uring_cmd: fix uring_cmd.c comments Yang Xiuwei
2026-07-02 17:19 ` Caleb Sander Mateos
2026-07-02 12:28 ` [PATCH 0/2] io_uring/uring_cmd cleanups 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=ce98e216-98bf-42cf-b1a0-89a2ea62f897@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=yangxiuwei@kylinos.cn \
/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