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.19-rc4
Date: Fri, 2 Jan 2026 09:08:54 -0700 [thread overview]
Message-ID: <787b104b-ffe0-47c7-9f8d-513847bcf6d3@kernel.dk> (raw)
Hi Linus,
Happy New Year! Here are a few fixes for io_uring that should go into
the 6.19 kernel release. This pull request contains:
- Removed dead argument length for io_uring_validate_mmap_request()
- Use GFP_NOWAIT for overflow CQEs on legacy ring setups rather than
GFP_ATOMIC, which makes it play nicer with memcg limits.
- Fix a potential circular locking issue with tctx node removal and
exec based cancelations.
Please pull!
The following changes since commit b14fad555302a2104948feaff70503b64c80ac01:
io_uring: fix filename leak in __io_openat_prep() (2025-12-25 07:58:33 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git tags/io_uring-6.19-20260102
for you to fetch changes up to 70eafc743016b1df73e00fd726ffedd44ce1bdd3:
io_uring/memmap: drop unused sz param in io_uring_validate_mmap_request() (2026-01-01 08:16:48 -0700)
----------------------------------------------------------------
io_uring-6.19-20260102
----------------------------------------------------------------
Alexandre Negrel (1):
io_uring: use GFP_NOWAIT for overflow CQEs on legacy rings
Caleb Sander Mateos (1):
io_uring/memmap: drop unused sz param in io_uring_validate_mmap_request()
Jens Axboe (1):
io_uring/tctx: add separate lock for list of tctx's in ctx
include/linux/io_uring_types.h | 8 +++++++-
io_uring/cancel.c | 5 +++++
io_uring/io_uring.c | 7 ++++++-
io_uring/memmap.c | 9 ++++-----
io_uring/register.c | 2 ++
io_uring/tctx.c | 8 ++++----
6 files changed, 28 insertions(+), 11 deletions(-)
--
Jens Axboe
next reply other threads:[~2026-01-02 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 16:08 Jens Axboe [this message]
2026-01-02 20:19 ` [GIT PULL] io_uring fixes for 6.19-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=787b104b-ffe0-47c7-9f8d-513847bcf6d3@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