public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
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-rc3
Date: Fri, 10 Jul 2026 22:30:17 -0600	[thread overview]
Message-ID: <ebf34c44-2a7b-4656-a9ff-528660a070c5@kernel.dk> (raw)

Hi Linus,

A set of io_uring fixes for 7.2-rc3. This contains:

- Restore full RCU read section in io_req_local_work_add(), which was
  mistakenly dropped with the DEFER_TASKRUN rework in this merge window.
  Revert the commit that grabbed the RCU read lock in
  io_ctx_mark_taskrun(), as that's no longer required with the previous
  fix.

- Fix a dangling iovec after a provided-buffer bundle grow failure, also
  an issue introduced in this merge window.

- Reject IORING_CQE_F_32 flag pass-through in MSG_RING to rings that
  weren't setup with CQE32 or CQE_MIXED.

- Return -EINVAL rather than -ENOMEM from get_unmapped_area() when mmap
  validation fails, matching io_uring_mmap().

Please pull!


The following changes since commit 3996771b8f759729cba0a28007438c085f814d61:

  io_uring/memmap: bound io_pin_pages() by page array byte size (2026-06-22 15:12:54 -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-20260710

for you to fetch changes up to f3176c8ac4217c88fe1147ab084c47092921ffc4:

  Revert "io_uring: grab RCU read lock marking task run" (2026-07-09 11:43:07 -0600)

----------------------------------------------------------------
io_uring-7.2-20260710

----------------------------------------------------------------
Hao-Yu Yang (1):
      io_uring: fix dangling iovec after provided-buffer bundle grow failure

Jens Axboe (1):
      Revert "io_uring: grab RCU read lock marking task run"

Melbin K Mathew (1):
      io_uring/msg_ring: reject CQE32 flag pass-through to normal rings

Woraphat Khiaodaeng (1):
      io_uring: restore RCU read section in io_req_local_work_add()

Yang Xiuwei (1):
      io_uring/uring_cmd: fix uring_cmd.c comments

Yi Xie (1):
      io_uring/memmap: return -EINVAL from get_unmapped_area() on bad mmap

 io_uring/kbuf.c      |  5 +++--
 io_uring/memmap.c    |  2 +-
 io_uring/msg_ring.c  | 34 +++++++++++++++++++++++++++-------
 io_uring/tw.c        |  9 ++++++---
 io_uring/uring_cmd.c |  4 ++--
 5 files changed, 39 insertions(+), 15 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2026-07-11  4:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11  4:30 Jens Axboe [this message]
2026-07-11 17:13 ` [GIT PULL] io_uring fixes for 7.2-rc3 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=ebf34c44-2a7b-4656-a9ff-528660a070c5@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