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.1-rc3
Date: Fri, 8 May 2026 13:19:14 -0600	[thread overview]
Message-ID: <db32ecb0-b37c-43b2-a8ab-cba6713b3e67@kernel.dk> (raw)

Hi Linus,

A few fixes for io_uring that should go into the current kernel release,
and will be heading to stable as well. This pull request contains:

- Ensure that the absolute timeouts for both the command side and the
  waiting side honor the callers time namespace.

- Ensure tracked NAPI entries are cleared at unregistration time, as
  the NAPI polling loop checks the list state rather than the general
  NAPI state. This can lead to NAPI polling even after unregistration
  has been done. If unregistered, all NAPI polling should be disabled.

- Fix for eventfd recursive invocation handling.

Please pull!


The following changes since commit 17666e2d7592c3e85260cafd3950121524acc2c5:

  io_uring/tw: serialize ctx->retry_llist with ->uring_lock (2026-04-30 06:57:20 -0600)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-7.1-20260508

for you to fetch changes up to 45d2b37a37ab98484693533496395c610a2cab96:

  io_uring/wait: honour caller's time namespace for IORING_ENTER_ABS_TIMER (2026-05-06 04:58:56 -0600)

----------------------------------------------------------------
io_uring-7.1-20260508

----------------------------------------------------------------
Maoyi Xie (2):
      io_uring/timeout: honour caller's time namespace for IORING_TIMEOUT_ABS
      io_uring/wait: honour caller's time namespace for IORING_ENTER_ABS_TIMER

Yufan Chen (2):
      io_uring/napi: clear tracked NAPI entries on unregister
      io_uring/eventfd: reset deferred signal state

 io_uring/eventfd.c |  1 +
 io_uring/napi.c    | 27 ++++++++++++++++++++-------
 io_uring/napi.h    |  8 +++++---
 io_uring/timeout.c | 35 ++++++++++++++++++++++-------------
 io_uring/wait.c    |  6 +++++-
 5 files changed, 53 insertions(+), 24 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2026-05-08 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 19:19 Jens Axboe [this message]
2026-05-08 20:42 ` [GIT PULL] io_uring fixes for 6.1-rc3 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-10-28 21:12 Jens Axboe
2022-10-30  1:29 ` 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=db32ecb0-b37c-43b2-a8ab-cba6713b3e67@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