From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>,
"[email protected]" <[email protected]>
Subject: [GIT PULL] Followup io_uring fixes for 5.9-rc4
Date: Sun, 6 Sep 2020 09:17:58 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Two followup fixes from the pull request on Friday that were done and
tested since. I deliberated on just waiting with these until the pull
request next week, but I think we should just get them in now. One is
fixing a regression from this merge window, the other are a followup
cancelation fix. Both have gone through full testing, and both spawned a
few new regression test additions to liburing.
- Don't play games with const, properly store the output iovec and
assign it as needed.
- Deferred request cancelation fix (Pavel)
Please pull!
The following changes since commit 355afaeb578abac907217c256a844cfafb0337b2:
io_uring: no read/write-retry on -EAGAIN error and O_NONBLOCK marked file (2020-09-02 10:20:41 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-5.9-2020-09-06
for you to fetch changes up to c127a2a1b7baa5eb40a7e2de4b7f0c51ccbbb2ef:
io_uring: fix linked deferred ->files cancellation (2020-09-05 16:02:42 -0600)
----------------------------------------------------------------
io_uring-5.9-2020-09-06
----------------------------------------------------------------
Jens Axboe (1):
io_uring: fix explicit async read/write mapping for large segments
Pavel Begunkov (2):
io_uring: fix cancel of deferred reqs with ->files
io_uring: fix linked deferred ->files cancellation
fs/io_uring.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++---
1 file changed, 52 insertions(+), 3 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-09-06 15:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 15:17 Jens Axboe [this message]
2020-09-06 19:14 ` [GIT PULL] Followup io_uring fixes for 5.9-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 \
[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