From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: Re: [PATCH] io_uring/fdinfo: cap SQ iteration at max SQ entries
Date: Mon, 27 Oct 2025 19:18:22 -0600 [thread overview]
Message-ID: <aQAZ3oCSkQFmbyPi@kbusch-mbp> (raw)
In-Reply-To: <85801cc1-082a-4383-877d-67cc181a50c6@kernel.dk>
On Mon, Oct 27, 2025 at 07:12:08PM -0600, Jens Axboe wrote:
> A previous commit changed the logic around how SQ entries are iterated,
> and as a result, had a few bugs. One is that it fully trusts the SQ
> head and tail, which are user exposed. Another is that it fails to
> increment the SQ head if the SQ index is out of range.
>
> Fix both of those up, reverting to the previous logic of how to
> iterate SQ entries.
Looks good.
Reviewed-by: Keith Busch <kbusch@kernel.org>
prev parent reply other threads:[~2025-10-28 1:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 1:12 [PATCH] io_uring/fdinfo: cap SQ iteration at max SQ entries Jens Axboe
2025-10-28 1:18 ` Keith Busch [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=aQAZ3oCSkQFmbyPi@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
/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