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.16-rc4
Date: Fri, 27 Jun 2025 08:25:24 -0600 [thread overview]
Message-ID: <681fa987-b28b-4669-82f2-d8d89966561e@kernel.dk> (raw)
Hi Linus,
Set of fixes for io_uring that should go into the 6.16 kernel release.
This pull request contains:
- Two tweaks for a recent fix: fixing a memory leak if multiple iovecs
were initially mapped but only the first was used and hence turned
into a UBUF rathan than an IOVEC iterator, and catching a case where a
retry would be done even if the previous segment wasn't full.
- Small series fixing an issue making the vm unhappy if debugging is
turned on, hitting a VM_BUG_ON_PAGE().
- Fix a resource leak in io_import_dmabuf() in the error handling case,
which is a regression in this merge window.
- Mark fallocate as needing to be write serialized, as is already done
for truncate and buffered writes.
Please pull!
The following changes since commit 51a4598ad5d9eb6be4ec9ba65bbfdf0ac302eb2e:
io_uring/net: always use current transfer count for buffer put (2025-06-20 08:33:45 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.16-20250626
for you to fetch changes up to 178b8ff66ff827c41b4fa105e9aabb99a0b5c537:
io_uring/kbuf: flag partial buffer mappings (2025-06-26 12:17:48 -0600)
----------------------------------------------------------------
io_uring-6.16-20250626
----------------------------------------------------------------
Fengnan Chang (1):
io_uring: make fallocate be hashed work
Jens Axboe (2):
io_uring/net: mark iov as dynamically allocated even for single segments
io_uring/kbuf: flag partial buffer mappings
Pavel Begunkov (3):
io_uring/rsrc: fix folio unpinning
io_uring/rsrc: don't rely on user vaddr alignment
io_uring: don't assume uaddr alignment in io_vec_fill_bvec
Penglei Jiang (1):
io_uring: fix resource leak in io_import_dmabuf()
io_uring/kbuf.c | 1 +
io_uring/kbuf.h | 3 ++-
io_uring/net.c | 34 +++++++++++++++++++++-------------
io_uring/opdef.c | 1 +
io_uring/rsrc.c | 30 ++++++++++++++++++++++--------
io_uring/rsrc.h | 1 +
io_uring/zcrx.c | 6 ++++--
7 files changed, 52 insertions(+), 24 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-06-27 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 14:25 Jens Axboe [this message]
2025-06-27 16:29 ` [GIT PULL] io_uring fixes for 6.16-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=681fa987-b28b-4669-82f2-d8d89966561e@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