public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.0-rc5
Date: Fri, 9 Sep 2022 11:24:19 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

A set of fixes that should go into the 6.0 release:

- Removed function that became unused after last weeks merge (Jiapeng)

- Two small fixes for kbuf recycling (Pavel)

- Include address copy for zc send for POLLFIRST (Pavel)

- Fix for short IO handling in the normal read/write path (Pavel)

Please pull!


The following changes since commit 916d72c10a4ca80ea51f1421e774cb765b53f28f:

  selftests/net: return back io_uring zc send tests (2022-09-01 09:13:33 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/io_uring-6.0-2022-09-09

for you to fetch changes up to 4d9cb92ca41dd8e905a4569ceba4716c2f39c75a:

  io_uring/rw: fix short rw error handling (2022-09-09 08:57:57 -0600)

----------------------------------------------------------------
io_uring-6.0-2022-09-09

----------------------------------------------------------------
Jiapeng Chong (1):
      io_uring/notif: Remove the unused function io_notif_complete()

Pavel Begunkov (4):
      io_uring/kbuf: fix not advancing READV kbuf ring
      io_uring: recycle kbuf recycle on tw requeue
      io_uring/net: copy addr for zc on POLL_FIRST
      io_uring/rw: fix short rw error handling

 io_uring/io_uring.c |  1 +
 io_uring/kbuf.h     |  8 ++++++--
 io_uring/net.c      |  7 ++++---
 io_uring/notif.c    |  8 --------
 io_uring/rw.c       | 30 ++++++++++++++++++------------
 5 files changed, 29 insertions(+), 25 deletions(-)

-- 
Jens Axboe

             reply	other threads:[~2022-09-09 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 17:24 Jens Axboe [this message]
2022-09-09 19:13 ` [GIT PULL] io_uring fixes for 6.0-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