From: Pavel Begunkov <asml.silence@gmail.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH v2] io_uring: check for user passing 0 nr_submit
Date: Wed, 22 Oct 2025 17:53:13 +0100 [thread overview]
Message-ID: <355c371d-124d-4414-9af4-fd9247692db3@gmail.com> (raw)
In-Reply-To: <x49sefbyrkk.fsf@segfault.usersys.redhat.com>
On 10/22/25 14:49, Jeff Moyer wrote:
> Pavel Begunkov <asml.silence@gmail.com> writes:
>
>> io_submit_sqes() shouldn't be stepping into its main loop when there is
>> nothing to submit, i.e. nr=0. Fix 0 submission queue entries checks,
>> which should follow after all user input truncations.
>
> I see two callers of io_submit_sqes, and neither of them will pass 0 for
> nr. What am I missing?
You're right, we can drop the fixes/stable part. It's still
good to have as it's handled not in the best way.
>> Cc: stable@vger.kernel.org
>> Fixes: 6962980947e2b ("io_uring: restructure submit sqes to_submit checks")
>> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
>> ---
>>
>> v2: split out of the series with extra tags, no functional changes
>>
>> io_uring/io_uring.c | 5 +++--
>> 1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
>> index 820ef0527666..ee04ab9bf968 100644
>> --- a/io_uring/io_uring.c
>> +++ b/io_uring/io_uring.c
>> @@ -2422,10 +2422,11 @@ int io_submit_sqes(struct io_ring_ctx *ctx, unsigned int nr)
>> unsigned int left;
>> int ret;
>>
>> + entries = min(nr, entries);
>> if (unlikely(!entries))
>> return 0;
>> - /* make sure SQ entry isn't read before tail */
>> - ret = left = min(nr, entries);
>> +
>> + ret = left = entries;
>> io_get_task_refs(left);
>> io_submit_state_start(&ctx->submit_state, left);
>
--
Pavel Begunkov
next prev parent reply other threads:[~2025-10-22 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 11:20 [PATCH v2] io_uring: check for user passing 0 nr_submit Pavel Begunkov
2025-10-22 13:49 ` Jeff Moyer
2025-10-22 16:53 ` Pavel Begunkov [this message]
2025-10-22 17:35 ` Jeff Moyer
2025-10-22 17:13 ` 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=355c371d-124d-4414-9af4-fd9247692db3@gmail.com \
--to=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=jmoyer@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