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 7.3-rc7
Date: Sun, 11 Oct 2026 07:11:25 -0600 [thread overview]
Message-ID: <51650716-bd0c-4349-92ff-01020abf6fac@kernel.dk> (raw)
Hi Linus,
io_uring fixes for the -rc7 kernel. This pull request contains:
- Don't spin on local work the exiting task can't run. For a ring still
R_DISABLED when the task got its tctx node, the submitter is set later
and may be another task, so DEFER_TASKRUN local work stays pending
forever and the exiting task spins in do_exit().
- Don't charge the SQ/CQ rings or provided buffer rings to
RLIMIT_MEMLOCK. The region API conversion started charging them, which
the rings had been exempt from.
- Don't exempt disabled rings from task restrictions on register
- Populate the CONNECT filter fields for a 24-byte sockaddr_in6
Please pull!
The following changes since commit a92193c91e8839fe5fc209616ea95465ae4b919d:
io_uring: fix task_work add use-after-free with SQPOLL (2026-09-29 06:52:39 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-7.3-20261010
for you to fetch changes up to fddcf4c5321b3ea5f72166c3fd36a9d1c34f80c7:
io_uring/cancel: don't spin on local work the task can't run (2026-10-09 08:33:09 -0600)
----------------------------------------------------------------
io_uring-7.3-20261010
----------------------------------------------------------------
Cen Zhang (Microsoft Security FORGE Labs) (1):
io_uring/cancel: don't spin on local work the task can't run
Eugene Gvozdetsky (1):
io_uring/register: don't exempt disabled rings from task restrictions
Hengyu Liang (1):
io_uring: do not charge the SQ/CQ rings to RLIMIT_MEMLOCK
Jens Axboe (1):
io_uring/kbuf: don't charge provided buffer rings to RLIMIT_MEMLOCK
Natasha Klaus (1):
io_uring/net: populate CONNECT filter fields for 24-byte sockaddr_in6
include/linux/io_uring_types.h | 2 ++
io_uring/cancel.c | 7 +++----
io_uring/io_uring.c | 13 ++++++++-----
io_uring/kbuf.c | 6 +++---
io_uring/memmap.c | 10 +++++-----
io_uring/memmap.h | 2 +-
io_uring/net.c | 4 +++-
io_uring/register.c | 21 +++++++++++++++------
io_uring/zcrx.c | 2 +-
9 files changed, 41 insertions(+), 26 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-10-11 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 13:11 Jens Axboe [this message]
2026-10-11 18:17 ` [GIT PULL] io_uring fixes for 7.3-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=51650716-bd0c-4349-92ff-01020abf6fac@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