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.18-rc6
Date: Fri, 14 Nov 2025 05:29:51 -0700 [thread overview]
Message-ID: <962882e4-207a-49a3-beb3-81067ead6681@kernel.dk> (raw)
Hi Linus,
Three small fixes for io_uring that should go into the 6.18 kernel
release. This pull request contains:
- Use the actual segments in a request when for bvec based buffers.
- Fix an odd case where the iovec might get leaked for a read/write
request, if it was newly allocated, overflowed the alloc cache, and
hit an early error.
- Minor tweak to the query API added in this release, returning the
number of available entries.
Please pull!
The following changes since commit 146eb58629f45f8297e83d69e64d4eea4b28d972:
io_uring: fix regbuf vector size truncation (2025-11-07 17:17:13 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-6.18-20251113
for you to fetch changes up to 2d0e88f3fd1dcb37072d499c36162baf5b009d41:
io_uring/rsrc: don't use blk_rq_nr_phys_segments() as number of bvecs (2025-11-12 08:25:33 -0700)
----------------------------------------------------------------
io_uring-6.18-20251113
----------------------------------------------------------------
Caleb Sander Mateos (1):
io_uring/rsrc: don't use blk_rq_nr_phys_segments() as number of bvecs
Jens Axboe (1):
io_uring/rw: ensure allocated iovec gets cleared for early failure
Pavel Begunkov (1):
io_uring/query: return number of available queries
include/uapi/linux/io_uring/query.h | 3 +++
io_uring/query.c | 2 ++
io_uring/rsrc.c | 16 +++++++++-------
io_uring/rw.c | 3 +++
4 files changed, 17 insertions(+), 7 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-11-14 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 12:29 Jens Axboe [this message]
2025-11-14 18:20 ` [GIT PULL] io_uring fixes for 6.18-rc6 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=962882e4-207a-49a3-beb3-81067ead6681@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