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-rc6
Date: Fri, 11 Jul 2025 07:47:44 -0600 [thread overview]
Message-ID: <bc75d13a-cea1-4a0d-a849-84b1379a1bc3@kernel.dk> (raw)
Hi Linus,
Set of fixes for io_uring that should go into the 6.16 kernel release.
This pull request contains:
- Remove a pointless warning in the zcrx code
- Fix for MSG_RING commands, where the allocated io_kiocb needs to be
freed under RCU as well.
- Revert the work-around we had in place for the anon inodes pretending
to be regular files. Since that got reworked upstream, the work-around
is no longer needed.
Please pull!
The following changes since commit 6f11adcc6f36ffd8f33dbdf5f5ce073368975bc3:
io_uring: gate REQ_F_ISREG on !S_ANON_INODE as well (2025-06-29 16:52:34 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.16-20250710
for you to fetch changes up to 9dff55ebaef7e94e5dedb6be28a1cafff65cc467:
Revert "io_uring: gate REQ_F_ISREG on !S_ANON_INODE as well" (2025-07-08 11:09:01 -0600)
----------------------------------------------------------------
io_uring-6.16-20250710
----------------------------------------------------------------
Jens Axboe (2):
io_uring/msg_ring: ensure io_kiocb freeing is deferred for RCU
Revert "io_uring: gate REQ_F_ISREG on !S_ANON_INODE as well"
Pavel Begunkov (1):
io_uring/zcrx: fix pp destruction warnings
include/linux/io_uring_types.h | 2 ++
io_uring/io_uring.c | 3 +--
io_uring/msg_ring.c | 4 ++--
io_uring/zcrx.c | 3 ---
4 files changed, 5 insertions(+), 7 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-07-11 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 13:47 Jens Axboe [this message]
2025-07-11 17:44 ` [GIT PULL] io_uring fixes for 6.16-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=bc75d13a-cea1-4a0d-a849-84b1379a1bc3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.