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.15-final
Date: Thu, 22 May 2025 13:56:34 -0600 [thread overview]
Message-ID: <a23908b7-210d-4037-8f86-48ceaae03453@kernel.dk> (raw)
Hi Linus,
A few fixes for io_uring that should go into the final 6.15 kernel
release:
- Kill a duplicate function definition, which can cause linking issues
in certain .config configurations. Introduced in this cycle.
- Fix for a potential overflow CQE reordering issue if a re-schedule is
done during posting. Heading to stable.
- Fix for an issue with recv bundles, where certain conditions can lead
to gaps in the buffers, where a contiguous buffer range was expected.
Heading to stable.
Please pull!
The following changes since commit d871198ee431d90f5308d53998c1ba1d5db5619a:
io_uring/fdinfo: grab ctx->uring_lock around io_uring_show_fdinfo() (2025-05-14 07:15:28 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.15-20250522
for you to fetch changes up to 3a08988123c868dbfdd054541b1090fb891fa49e:
io_uring/net: only retry recv bundle for a full transfer (2025-05-21 19:24:18 -0600)
----------------------------------------------------------------
io_uring-6.15-20250522
----------------------------------------------------------------
Caleb Sander Mateos (1):
io_uring/cmd: axe duplicate io_uring_cmd_import_fixed_vec() declaration
Jens Axboe (1):
io_uring/net: only retry recv bundle for a full transfer
Pavel Begunkov (1):
io_uring: fix overflow resched cqe reordering
io_uring/io_uring.c | 1 +
io_uring/net.c | 14 ++++++++++----
io_uring/uring_cmd.h | 6 ------
3 files changed, 11 insertions(+), 10 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-05-22 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 19:56 Jens Axboe [this message]
2025-05-22 20:16 ` [GIT PULL] io_uring fixes for 6.15-final 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=a23908b7-210d-4037-8f86-48ceaae03453@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