From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.14-rc3
Date: Fri, 14 Feb 2025 10:28:32 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Set of fixes for io_uring that should go into the 6.14-rc3 kernel
release. This pull request contains:
- Set of fixes for a potential data corruption issue with
IORING_OP_URING_CMD, where not all the SQE data is stable. Will be
revisited in the future, for now it ends up with just always copying
it beyond prep to provide the same guarantees as all other opcodes.
- Make the waitid opcode setup async data like any other opcodes. No
real fix here, just a consistency thing.
- Fix for waitid io_tw_state abuse.
- When a buffer group is type is changed, do so by allocating a new
buffer group entry and discard the old one, rather than migrating.
Please pull!
The following changes since commit 8c8492ca64e79c6e0f433e8c9d2bcbd039ef83d0:
io_uring/net: don't retry connect operation on EPOLLERR (2025-01-30 09:41:25 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.14-20250214
for you to fetch changes up to d6211ebbdaa541af197b50b8dd8f22642ce0b87f:
io_uring/uring_cmd: unconditionally copy SQEs at prep time (2025-02-13 10:24:39 -0700)
----------------------------------------------------------------
io_uring-6.14-20250214
----------------------------------------------------------------
Caleb Sander Mateos (2):
io_uring/uring_cmd: don't assume io_uring_cmd_data layout
io_uring/uring_cmd: switch sqe to async_data on EAGAIN
Jens Axboe (3):
io_uring/uring_cmd: remove dead req_has_async_data() check
io_uring/waitid: setup async data in the prep handler
io_uring/uring_cmd: unconditionally copy SQEs at prep time
Pavel Begunkov (2):
io_uring/waitid: don't abuse io_tw_state
io_uring/kbuf: reallocate buf lists on upgrade
io_uring/kbuf.c | 16 ++++++++++++----
io_uring/uring_cmd.c | 28 +++++++++-------------------
io_uring/waitid.c | 18 +++++++++---------
3 files changed, 30 insertions(+), 32 deletions(-)
--
Jens Axboe
next reply other threads:[~2025-02-14 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 17:28 Jens Axboe [this message]
2025-02-14 22:54 ` [GIT PULL] io_uring fixes for 6.14-rc3 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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