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.10-rc
Date: Fri, 20 Nov 2020 11:45:31 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Mostly regression or stable fodder:
- Disallow async path resolution of /proc/self
- Tighten constraints for segmented async buffered reads
- Fix double completion for a retry error case
- Fix for fixed file life times (Pavel)
Please pull!
The following changes since commit 88ec3211e46344a7d10cf6cb5045f839f7785f8e:
io_uring: round-up cq size before comparing with rounded sq size (2020-11-11 10:42:41 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-5.10-2020-11-20
for you to fetch changes up to e297822b20e7fe683e107aea46e6402adcf99c70:
io_uring: order refnode recycling (2020-11-18 08:02:10 -0700)
----------------------------------------------------------------
io_uring-5.10-2020-11-20
----------------------------------------------------------------
Jens Axboe (4):
proc: don't allow async path resolution of /proc/self components
io_uring: handle -EOPNOTSUPP on path resolution
mm: never attempt async page lock if we've transferred data already
io_uring: don't double complete failed reissue request
Pavel Begunkov (2):
io_uring: get an active ref_node from files_data
io_uring: order refnode recycling
fs/io_uring.c | 57 ++++++++++++++++++++++++++++++++++++++++++---------------
fs/proc/self.c | 7 +++++++
mm/filemap.c | 18 ++++++++++++++----
3 files changed, 63 insertions(+), 19 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-11-20 18:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 18:45 Jens Axboe [this message]
2020-11-20 20:02 ` [GIT PULL] io_uring fixes for 5.10-rc Linus Torvalds
2020-11-20 21:36 ` Jens Axboe
2020-11-21 0:23 ` Linus Torvalds
2020-11-21 2:41 ` Jens Axboe
2020-11-21 3:00 ` Jens Axboe
2020-11-21 18:07 ` Linus Torvalds
2020-11-21 22:58 ` Jens Axboe
2020-12-10 17:32 ` namei.c LOOKUP_NONBLOCK (was "Re: [GIT PULL] io_uring fixes for 5.10-rc") Jens Axboe
2020-12-10 18:55 ` Linus Torvalds
2020-12-10 19:21 ` Jens Axboe
2020-11-21 0:29 ` [GIT PULL] io_uring fixes for 5.10-rc pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-11-27 20:47 Jens Axboe
2020-11-27 21:21 ` pr-tracker-bot
2020-11-13 21:18 Jens Axboe
2020-11-14 0:15 ` pr-tracker-bot
2020-11-07 20:13 Jens Axboe
2020-11-07 22:08 ` pr-tracker-bot
2020-10-30 17:09 Jens Axboe
2020-10-30 22:10 ` 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