From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 5.19-rc5
Date: Fri, 1 Jul 2022 09:31:56 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Two minor tweaks:
- While we still can, adjust the send/recv based flags to be in ->ioprio
rather than in ->addr2. This is consistent with eg accept, and also
doesn't waste a full 64-bit field for flags (Pavel).
- 5.18-stable fix for re-importing provided buffers. Not much real world
relevance here as it'll only impact non-pollable files gone async,
which is more of a practical test case rather than something that is
used in the wild (Dylan).
Please pull!
The following changes since commit 386e4fb6962b9f248a80f8870aea0870ca603e89:
io_uring: use original request task for inflight tracking (2022-06-23 11:06:43 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-5.19-2022-07-01
for you to fetch changes up to 09007af2b627f0f195c6c53c4829b285cc3990ec:
io_uring: fix provided buffer import (2022-06-30 11:34:41 -0600)
----------------------------------------------------------------
io_uring-5.19-2022-07-01
----------------------------------------------------------------
Dylan Yudaken (1):
io_uring: fix provided buffer import
Pavel Begunkov (1):
io_uring: keep sendrecv flags in ioprio
fs/io_uring.c | 19 ++++++++++++-------
include/uapi/linux/io_uring.h | 2 +-
2 files changed, 13 insertions(+), 8 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-07-01 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 15:31 Jens Axboe [this message]
2022-07-01 18:02 ` [GIT PULL] io_uring fixes for 5.19-rc5 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