From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Cc: Caleb Sander Mateos <csander@purestorage.com>
Subject: Re: [PATCH V2] io_uring: fix buffer auto-commit for multishot uring_cmd
Date: Thu, 23 Oct 2025 19:53:48 -0600 [thread overview]
Message-ID: <176127082821.7812.5952214714775561667.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251024013459.2591830-1-ming.lei@redhat.com>
On Fri, 24 Oct 2025 09:34:59 +0800, Ming Lei wrote:
> Commit 620a50c92700 ("io_uring: uring_cmd: add multishot support") added
> multishot uring_cmd support with explicit buffer upfront commit via
> io_uring_mshot_cmd_post_cqe(). However, the buffer selection path in
> io_ring_buffer_select() was auto-committing buffers for non-pollable files,
> which conflicts with uring_cmd's explicit upfront commit model.
>
> This way consumes the whole selected buffer immediately, and causes
> failure on the following buffer selection.
>
> [...]
Applied, thanks!
[1/1] io_uring: fix buffer auto-commit for multishot uring_cmd
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-10-24 1:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 1:34 [PATCH V2] io_uring: fix buffer auto-commit for multishot uring_cmd Ming Lei
2025-10-24 1:53 ` Jens Axboe [this message]
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=176127082821.7812.5952214714775561667.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=csander@purestorage.com \
--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