From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 5.7-rc4
Date: Fri, 1 May 2020 16:52:38 -0600 [thread overview]
Message-ID: <8bd7dea4-76f7-cb50-7658-3a3d50539edf@kernel.dk> (raw)
Hi Linus,
- Fix for statx not grabbing the file table, making AT_EMPTY_PATH fail
- Cover a few cases where async poll can handle retry, eliminating the
need for an async thread
- fallback request busy/free fix (Bijan)
- syzbot reported SQPOLL thread exit fix for non-preempt (Xiaoguang)
- Fix extra put of req for sync_file_range (Pavel)
- Always punt splice async. We'll improve this for 5.8, but wanted to
eliminate the inode mutex lock from the non-blocking path for 5.7
(Pavel)
Please pull!
git://git.kernel.dk/linux-block.git tags/io_uring-5.7-2020-05-01
----------------------------------------------------------------
Bijan Mottahedeh (1):
io_uring: use proper references for fallback_req locking
Jens Axboe (3):
io_uring: statx must grab the file table for valid fd
io_uring: enable poll retry for any file with ->read_iter / ->write_iter
io_uring: only force async punt if poll based retry can't handle it
Pavel Begunkov (3):
io_uring: fix extra put in sync_file_range()
io_uring: check non-sync defer_list carefully
io_uring: punt splice async because of inode mutex
Xiaoguang Wang (1):
io_uring: use cond_resched() in io_ring_ctx_wait_and_kill()
fs/io_uring.c | 58 +++++++++++++++++++++++++++++++---------------------------
1 file changed, 31 insertions(+), 27 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-05-01 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 22:52 Jens Axboe [this message]
2020-05-02 0:40 ` [GIT PULL] io_uring fixes for 5.7-rc4 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=8bd7dea4-76f7-cb50-7658-3a3d50539edf@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@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 NNTP newsgroup(s).