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 6.18-rc2
Date: Fri, 17 Oct 2025 04:26:14 -0600	[thread overview]
Message-ID: <24ba2aad-762e-4fa1-bbf8-2956999a65c5@kernel.dk> (raw)

Hi Linus,

A small set of fixes for io_uring that should go into this release. This
pull request contains:

- Revert of a change that went into an older kernel, and which has been
  reported to cause a regression for some write workloads on LVM while a
  snapshop is being created.

- Fix a regression from this merge window, where some compilers (and/or
  certain .config options) would cause an earlier evaluations of a
  dereference which would then cause a NULL pointer dereference. I was
  only able to reproduce this with OPTIMIZE_FOR_SIZE=y, but David
  Howells hit it with just KASAN enabled. Depending on how things
  inlined, this makes sense.

- Fix for a missing lock around a mem region unregistration.

- Fix for ring resizing with the same placement after resize.

Please pull!


The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:

  Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-6.18-20251016

for you to fetch changes up to 18d6b1743eafeb3fb1e0ea5a2b7fd0a773d525a8:

  io_uring/rw: check for NULL io_br_sel when putting a buffer (2025-10-15 13:38:53 -0600)

----------------------------------------------------------------
io_uring-6.18-20251016

----------------------------------------------------------------
Jens Axboe (2):
      Revert "io_uring/rw: drop -EOPNOTSUPP check in __io_complete_rw_common()"
      io_uring/rw: check for NULL io_br_sel when putting a buffer

Pavel Begunkov (2):
      io_uring: protect mem region deregistration
      io_uring: fix unexpected placement on same size resizing

 io_uring/register.c | 8 +-------
 io_uring/rw.c       | 8 ++++++--
 2 files changed, 7 insertions(+), 9 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2025-10-17 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 10:26 Jens Axboe [this message]
2025-10-17 15:55 ` [GIT PULL] io_uring fixes for 6.18-rc2 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=24ba2aad-762e-4fa1-bbf8-2956999a65c5@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