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
