Linux io-uring development
 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.13-rc4
Date: Fri, 20 Dec 2024 09:24:27 -0700	[thread overview]
Message-ID: <785290eb-4182-4ea0-bce1-b3d895de09bf@kernel.dk> (raw)

Hi Linus,

Fixes for io_uring that should go into the 6.13-rc4 kernel release. This
pull request contains:

- Fix for a file ref leak for registered ring fds

- Turn the ->timeout_lock into a raw spinlock, as it nests under the
  io-wq lock which is a raw spinlock as it's called from the scheduler
  side

- Limit ring resizing to DEFER_TASKRUN for now. We will broaden this in
  the future, but for now, ensure that it's only feasible on rings with
  a single user

- Add sanity check for io-wq enqueuing

Please pull!


The following changes since commit 99d6af6e8a22b792e1845b186f943cd10bb4b7b0:

  io_uring/rsrc: don't put/free empty buffers (2024-12-12 08:01:52 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.13-20241220

for you to fetch changes up to dbd2ca9367eb19bc5e269b8c58b0b1514ada9156:

  io_uring: check if iowq is killed before queuing (2024-12-19 13:31:53 -0700)

----------------------------------------------------------------
io_uring-6.13-20241220

----------------------------------------------------------------
Jann Horn (1):
      io_uring: Fix registered ring file refcount leak

Jens Axboe (2):
      io_uring: make ctx->timeout_lock a raw spinlock
      io_uring/register: limit ring resizing to DEFER_TASKRUN

Pavel Begunkov (1):
      io_uring: check if iowq is killed before queuing

 include/linux/io_uring.h       |  4 +---
 include/linux/io_uring_types.h |  2 +-
 io_uring/io_uring.c            | 17 +++++++++++------
 io_uring/register.c            |  3 +++
 io_uring/timeout.c             | 40 ++++++++++++++++++++--------------------
 5 files changed, 36 insertions(+), 30 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2024-12-20 16:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 16:24 Jens Axboe [this message]
2024-12-20 22:12 ` [GIT PULL] io_uring fixes for 6.13-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=785290eb-4182-4ea0-bce1-b3d895de09bf@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