From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 6.17-rc4
Date: Thu, 28 Aug 2025 19:27:47 -0600 [thread overview]
Message-ID: <6a3bb8be-140e-4ec4-b903-683c43115992@kernel.dk> (raw)
Hi Linus,
Two fixes for the ring provided buffers in this pull request:
- Use the proper type for min_t() in getting the min of the leftover
bytes and the buffer length.
- As good practice, use READ_ONCE() consistently for reading ring
provided buffer lengths. Additionally, stop looping for incremental
commits if a zero sized buffer is hit, as no further progress can be
made at that point.
Please pull!
The following changes since commit e4e6aaea46b7be818eba0510ba68d30df8689ea3:
io_uring: clear ->async_data as part of normal init (2025-08-21 13:54:01 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.17-20250828
for you to fetch changes up to 98b6fa62c84f2e129161e976a5b9b3cb4ccd117b:
io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths (2025-08-28 05:48:34 -0600)
----------------------------------------------------------------
io_uring-6.17-20250828
----------------------------------------------------------------
Jens Axboe (1):
io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths
Qingyue Zhang (1):
io_uring/kbuf: fix signedness in this_len calculation
io_uring/kbuf.c | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-08-29 1:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 1:27 Jens Axboe [this message]
2025-08-29 16:39 ` [GIT PULL] io_uring fixes for 6.17-rc4 pr-tracker-bot
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=6a3bb8be-140e-4ec4-b903-683c43115992@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=torvalds@linux-foundation.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