From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.7-rc1
Date: Fri, 10 Nov 2023 10:32:51 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Mostly just a few fixes and cleanups caused by the read multishot
support. Outside of that, a stable fix for how a connect retry is done.
Please pull!
The following changes since commit 8f6f76a6a29f36d2f3e4510d0bde5046672f6924:
Merge tag 'mm-nonmm-stable-2023-11-02-14-08' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2023-11-02 20:53:31 -1000)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.7-2023-11-10
for you to fetch changes up to e53759298a7d7e98c3e5c2440d395d19cea7d6bf:
io_uring: do not clamp read length for multishot read (2023-11-06 13:41:58 -0700)
----------------------------------------------------------------
io_uring-6.7-2023-11-10
----------------------------------------------------------------
Dylan Yudaken (3):
io_uring: indicate if io_kbuf_recycle did recycle anything
io_uring: do not allow multishot read to set addr or len
io_uring: do not clamp read length for multishot read
Jens Axboe (4):
io_uring/rw: don't attempt to allocate async data if opcode doesn't need it
io_uring/net: ensure socket is marked connected on connect retry
io_uring/rw: add separate prep handler for readv/writev
io_uring/rw: add separate prep handler for fixed read/write
io_uring/kbuf.c | 6 ++---
io_uring/kbuf.h | 13 ++++++----
io_uring/net.c | 24 +++++++++----------
io_uring/opdef.c | 8 +++----
io_uring/rw.c | 72 ++++++++++++++++++++++++++++++++++++++++----------------
io_uring/rw.h | 2 ++
6 files changed, 80 insertions(+), 45 deletions(-)
--
Jens Axboe
next reply other threads:[~2023-11-10 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 17:32 Jens Axboe [this message]
2023-11-10 19:28 ` [GIT PULL] io_uring fixes for 6.7-rc1 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