From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fix for 5.5-rc
Date: Fri, 10 Jan 2020 11:07:17 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
Single fix for this series, fixing a regression with the short read
handling. This just removes it, as it cannot safely be done for all
cases.
Please pull!
git://git.kernel.dk/linux-block.git tags/io_uring-5.5-2020-01-10
----------------------------------------------------------------
Jens Axboe (1):
io_uring: remove punt of short reads to async context
fs/io_uring.c | 12 ------------
1 file changed, 12 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-01-10 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 18:07 Jens Axboe [this message]
2020-01-10 20:26 ` [GIT PULL] io_uring fix for 5.5-rc Linus Torvalds
2020-01-10 20:32 ` Jens Axboe
2020-01-10 20:34 ` Linus Torvalds
2020-01-10 20:36 ` Jens Axboe
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] \
/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