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.7-rc
Date: Fri, 22 May 2020 11:12:07 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A small collection of small fixes that should go into this release:
- Two fixes for async request preparation (Pavel)
- Busy clear fix for SQPOLL (Xiaoguang)
- Don't use kiocb->private for O_DIRECT buf index, some file systems use
it (Bijan)
- Kill dead check in io_splice()
- Ensure sqo_wait is initialized early
- Cancel task_work if we fail adding to original process
- Only add (IO)pollable requests to iopoll list, fixing a regression in
this merge window.
Please pull!
git://git.kernel.dk/linux-block.git tags/io_uring-5.7-2020-05-22
----------------------------------------------------------------
Bijan Mottahedeh (1):
io_uring: don't use kiocb.private to store buf_index
Jens Axboe (4):
io_uring: initialize ctx->sqo_wait earlier
io_uring: remove dead check in io_splice()
io_uring: cancel work if task_work_add() fails
io_uring: don't add non-IO requests to iopoll pending list
Pavel Begunkov (2):
io_uring: don't prepare DRAIN reqs twice
io_uring: fix FORCE_ASYNC req preparation
Xiaoguang Wang (1):
io_uring: reset -EBUSY error when io sq thread is waken up
fs/io_uring.c | 60 +++++++++++++++++++++++++++++++++--------------------------
1 file changed, 34 insertions(+), 26 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-05-22 17:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 17:12 Jens Axboe [this message]
2020-05-22 19:05 ` [GIT PULL] io_uring fixes for 5.7-rc pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-04-17 15:16 Jens Axboe
2020-04-17 17:26 ` Linus Torvalds
2020-04-17 17:27 ` Linus Torvalds
2020-04-17 17:42 ` Jens Axboe
2020-04-17 17:45 ` 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