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.0-rc4
Date: Fri, 13 Mar 2026 05:47:11 -0600 [thread overview]
Message-ID: <0ee80082-40b4-462d-9661-142cfb67a56c@kernel.dk> (raw)
Hi Linus,
Set of fixes for io_uring that should go into the 7.0 kernel release.
This pull request contains:
- Fix an inverted true/false comment on task_no_new_privs, from the BPF
filtering changes merged in this release.
- Use the migration disabling way of running the BPF filters, as the
io_uring side doesn't do that already.
- Fix an issue with ->rings stability under resize, both for local
task_work additions and for eventfd signaling.
- Fix an issue with SQE mixed mode, where a bounds check wasn't correct
for having a 128b SQE.
- Fix an issue where a legacy provided buffer group is changed to to
ring mapped one while legacy buffers from that group are in flight.
Please pull!
The following changes since commit 531bb98a030cc1073bd7ed9a502c0a3a781e92ee:
io_uring/zcrx: use READ_ONCE with user shared RQEs (2026-03-04 06:30:39 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-7.0-20260312
for you to fetch changes up to c2c185be5c85d37215397c8e8781abf0a69bec1f:
io_uring/kbuf: check if target buffer list is still legacy on recycle (2026-03-12 08:59:25 -0600)
----------------------------------------------------------------
io_uring-7.0-20260312
----------------------------------------------------------------
Jann Horn (1):
io_uring/register: fix comment about task_no_new_privs
Jens Axboe (4):
io_uring/bpf_filter: use bpf_prog_run_pin_on_cpu() to prevent migration
io_uring: ensure ctx->rings is stable for task work flags manipulation
io_uring/eventfd: use ctx->rings_rcu for flags checking
io_uring/kbuf: check if target buffer list is still legacy on recycle
Tom Ryan (1):
io_uring: fix physical SQE bounds check for SQE_MIXED 128-byte ops
include/linux/io_uring_types.h | 1 +
io_uring/bpf_filter.c | 2 +-
io_uring/eventfd.c | 10 +++++++---
io_uring/io_uring.c | 4 +++-
io_uring/kbuf.c | 13 +++++++++++--
io_uring/register.c | 15 +++++++++++++--
io_uring/tw.c | 22 ++++++++++++++++++++--
7 files changed, 56 insertions(+), 11 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-03-13 11:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 11:47 Jens Axboe [this message]
2026-03-13 17:33 ` [GIT PULL] io_uring fixes for 7.0-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=0ee80082-40b4-462d-9661-142cfb67a56c@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