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-rc7
Date: Fri, 19 Sep 2025 07:52:07 -0600 [thread overview]
Message-ID: <7102d62a-bc57-4bd3-b74f-201a35c770c2@kernel.dk> (raw)
Hi Linus,
Set of fixes for io_uring that should go into the 6.17 kernel release.
This pull request contains:
- Fix for a regression introduced in the io-wq worker creation logic.
- Remove the allocation cache for the msg_ring io_kiocb allocations. I
have a suspicion that there's a bug there, and since we just fixed one
in that area, let's just yank the use of that cache entirely. It's not
that important, and it kills some code.
- Treat a closed ring like task exiting in that any requests that
trigger post that condition should just get canceled. Doesn't fix any
real issues, outside of having tasks being able to rely on that
guarantee.
- Fix for a bug in the network zero-copy notification mechanism, where a
comparison for matching tctx/ctx for notifications was buggy in that
it didn't correctly compare with the previous notification.
Please pull!
The following changes since commit 98b6fa62c84f2e129161e976a5b9b3cb4ccd117b:
io_uring/kbuf: always use READ_ONCE() to read ring provided buffer lengths (2025-08-28 05:48:34 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.17-20250919
for you to fetch changes up to 2c139a47eff8de24e3350dadb4c9d5e3426db826:
io_uring: fix incorrect io_kiocb reference in io_link_skb (2025-09-19 06:00:57 -0600)
----------------------------------------------------------------
io_uring-6.17-20250919
----------------------------------------------------------------
Jens Axboe (2):
io_uring: include dying ring in task_work "should cancel" state
io_uring/msg_ring: kill alloc_cache for io_kiocb allocations
Max Kellermann (1):
io_uring/io-wq: fix `max_workers` breakage and `nr_workers` underflow
Yang Xiuwei (1):
io_uring: fix incorrect io_kiocb reference in io_link_skb
include/linux/io_uring_types.h | 3 ---
io_uring/io-wq.c | 6 +++---
io_uring/io_uring.c | 10 ++++------
io_uring/io_uring.h | 4 ++--
io_uring/msg_ring.c | 24 ++----------------------
io_uring/notif.c | 2 +-
io_uring/poll.c | 2 +-
io_uring/timeout.c | 2 +-
io_uring/uring_cmd.c | 2 +-
9 files changed, 15 insertions(+), 40 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-09-19 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 13:52 Jens Axboe [this message]
2025-09-19 20:18 ` [GIT PULL] io_uring fixes for 6.17-rc7 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=7102d62a-bc57-4bd3-b74f-201a35c770c2@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