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] Followup io_uring fixes for 6.19-rc1
Date: Mon, 8 Dec 2025 13:31:06 -0700	[thread overview]
Message-ID: <fdab55a9-8a66-40e4-b824-b473b63c974b@kernel.dk> (raw)

Hi Linus,

Followup set of fixes for io_uring for this merge window. These are
either later fixes, or cleanups that don't make sense to defer. This
pull request contains:

- Fix for a recent regression in io-wq worker creation.

- Tracing cleanup

- Use READ_ONCE/WRITE_ONCE consistently for ring mapped kbufs. Mostly
  for documentation purposes, indicating that they are shared with
  userspace.

- Fix for POLL_ADD losing a completion, if the request is updated and
  now is triggerable - eg, if POLLIN is set with the updated, and the
  polled file is readable.

- In conjunction with the above fix, also unify how poll wait queue
  entries are deleted with the head update. We had 3 different spots
  doing both the list deletion and head write, with one of them nicely
  documented. Abstract that into a helper and use it consistently.

- Small series from Joanne fixing an issue with buffer cloning, and
  cleaning up the arg validation.

Please pull!


The following changes since commit 559e608c46553c107dbba19dae0854af7b219400:

  Merge tag 'ntfs3_for_6.19' of https://github.com/Paragon-Software-Group/linux-ntfs3 (2025-12-03 20:45:43 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-6.19-20251208

for you to fetch changes up to 55d57b3bcc7efcab812a8179e2dc17d781302997:

  io_uring/poll: unify poll waitqueue entry and list removal (2025-12-05 10:23:28 -0700)

----------------------------------------------------------------
io_uring-6.19-20251208

----------------------------------------------------------------
Caleb Sander Mateos (3):
      io_uring/io-wq: always retry worker create on ERESTART*
      io_uring/trace: rename io_uring_queue_async_work event "rw" field
      io_uring/kbuf: use READ_ONCE() for userspace-mapped memory

Jens Axboe (2):
      io_uring/poll: correctly handle io_poll_add() return value on update
      io_uring/poll: unify poll waitqueue entry and list removal

Joanne Koong (4):
      io_uring/rsrc: clean up buffer cloning arg validation
      io_uring/rsrc: rename misleading src_node variable in io_clone_buffers()
      io_uring/rsrc: fix lost entries after cloned range
      io_uring/kbuf: use WRITE_ONCE() for userspace-shared buffer ring fields

 include/trace/events/io_uring.h | 12 +++++-----
 io_uring/io-wq.c                |  5 ++--
 io_uring/kbuf.c                 | 16 ++++++-------
 io_uring/poll.c                 | 52 +++++++++++++++++++++++------------------
 io_uring/rsrc.c                 | 47 +++++++++++++++++--------------------
 5 files changed, 67 insertions(+), 65 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2025-12-08 20:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 20:31 Jens Axboe [this message]
2025-12-09  0:12 ` [GIT PULL] Followup io_uring fixes for 6.19-rc1 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=fdab55a9-8a66-40e4-b824-b473b63c974b@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