From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>,
"[email protected]" <[email protected]>
Subject: [GIT PULL] io_uring fixes for 5.9-rc2
Date: Fri, 21 Aug 2020 14:53:38 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A few io_uring fixes:
- Make sure the head link cancelation includes async work
- Get rid of kiocb_wait_page_queue_init(), makes no sense to have it as
a separate function since you moved it into io_uring itself
- io_import_iovec cleanups (Pavel, me)
- Use system_unbound_wq for ring exit work, to avoid spawning tons of
these if we have tons of rings exiting at the same time
- Fix req->flags overflow flag manipulation (Pavel)
Please pull!
The following changes since commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5:
Linux 5.9-rc1 (2020-08-16 13:04:57 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-5.9-2020-08-21
for you to fetch changes up to 867a23eab52847d41a0a6eae41a64d76de7782a8:
io_uring: kill extra iovec=NULL in import_iovec() (2020-08-20 05:36:19 -0600)
----------------------------------------------------------------
io_uring-5.9-2020-08-21
----------------------------------------------------------------
Jens Axboe (4):
io_uring: find and cancel head link async work on files exit
io_uring: get rid of kiocb_wait_page_queue_init()
io_uring: cleanup io_import_iovec() of pre-mapped request
io_uring: use system_unbound_wq for ring exit work
Pavel Begunkov (3):
io_uring: fix racy req->flags modification
io_uring: comment on kfree(iovec) checks
io_uring: kill extra iovec=NULL in import_iovec()
fs/io_uring.c | 173 +++++++++++++++++++++++++++-------------------------------
1 file changed, 79 insertions(+), 94 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-08-21 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 20:53 Jens Axboe [this message]
2020-08-21 22:06 ` [GIT PULL] io_uring fixes for 5.9-rc2 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] \
[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