From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 6.9-rc3
Date: Fri, 5 Apr 2024 14:46:55 -0600 [thread overview]
Message-ID: <ceeb1b95-070a-4812-8a43-12a638da4c94@kernel.dk> (raw)
Hi Linus,
Some fixes that should go into the 6.9 kernel release:
- Backport of some fixes that came up during development of the 6.10
io_uring patches. This includes some kbuf cleanups and reference
fixes.
- Disable multishot read if we don't have NOWAIT support on the target
- Fix for a dependency issue with workqueue flushing
Please pull!
The following changes since commit 39cd87c4eb2b893354f3b850f916353f2658ae6f:
Linux 6.9-rc2 (2024-03-31 14:32:39 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux.git tags/io_uring-6.9-20240405
for you to fetch changes up to 561e4f9451d65fc2f7eef564e0064373e3019793:
io_uring/kbuf: hold io_buffer_list reference over mmap (2024-04-02 19:03:27 -0600)
----------------------------------------------------------------
io_uring-6.9-20240405
----------------------------------------------------------------
Jens Axboe (7):
io_uring/rw: don't allow multishot reads without NOWAIT support
io_uring: disable io-wq execution of multishot NOWAIT requests
io_uring: use private workqueue for exit work
io_uring/kbuf: get rid of lower BGID lists
io_uring/kbuf: get rid of bl->is_ready
io_uring/kbuf: protect io_buffer_list teardown with a reference
io_uring/kbuf: hold io_buffer_list reference over mmap
include/linux/io_uring_types.h | 1 -
io_uring/io_uring.c | 31 ++++++-----
io_uring/kbuf.c | 118 ++++++++++++++---------------------------
io_uring/kbuf.h | 8 +--
io_uring/rw.c | 9 +++-
5 files changed, 73 insertions(+), 94 deletions(-)
--
Jens Axboe
next reply other threads:[~2024-04-05 20:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 20:46 Jens Axboe [this message]
2024-04-06 0:10 ` [GIT PULL] io_uring fixes for 6.9-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 \
--in-reply-to=ceeb1b95-070a-4812-8a43-12a638da4c94@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).