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.2-rc4
Date: Sun, 19 Jul 2026 08:39:40 -0600 [thread overview]
Message-ID: <6c68b461-0e7b-45ed-8e13-d7b7fd29b65b@kernel.dk> (raw)
Hi Linus,
A small set of io_uring fixes for this week. This pull request contains:
- Fix a use-after-free in the bpf-ops struct_ops path, where the same
io_uring_bpf_ops map could be registered more than once.
- Fix the deferred iovec free for the provided-buffer grow path, which
could leave the caller with a dangling iovec and result in repeated
frees. Follow-up to the earlier fix in this series.
- Zero-check the unused addr3/pad2 SQE fields for unlinkat
Please pull!
The following changes since commit f3176c8ac4217c88fe1147ab084c47092921ffc4:
Revert "io_uring: grab RCU read lock marking task run" (2026-07-09 11:43:07 -0600)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-7.2-20260717
for you to fetch changes up to 3afc64c61ce906a04f073ca350b46de10e8302f9:
io_uring/bpf-ops: reject re-registration of an already-bound ops (2026-07-17 11:17:54 -0600)
----------------------------------------------------------------
Jaeyeong Lee (1):
io_uring/kbuf: free the replaced iovec after a successful grow
Woraphat Khiaodaeng (1):
io_uring/bpf-ops: reject re-registration of an already-bound ops
Yi Xie (1):
io_uring/fs: check unused sqe fields for unlinkat
io_uring/bpf-ops.c | 2 ++
io_uring/fs.c | 3 ++-
io_uring/kbuf.c | 4 ++--
3 files changed, 6 insertions(+), 3 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-07-19 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 14:39 Jens Axboe [this message]
2026-07-19 16:45 ` [GIT PULL] io_uring fixes for 7.2-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=6c68b461-0e7b-45ed-8e13-d7b7fd29b65b@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