From: Pavel Begunkov <[email protected]>
To: Alexander Viro <[email protected]>,
[email protected], Jens Axboe <[email protected]>,
[email protected]
Cc: [email protected], [email protected]
Subject: [PATCH 0/2] iter revert problems
Date: Mon, 9 Aug 2021 12:52:35 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
For the bug description see 2/2. As mentioned there the current problems
is because of generic_write_checks(), but there was also a similar case
fixed in 5.12, which should have been triggerable by normal
write(2)/read(2) and others.
It may be better to enforce reexpands as a long term solution, but for
now this patchset is quickier and easier to backport.
Pavel Begunkov (2):
iov_iter: mark truncated iters
io_uring: don't retry with truncated iter
fs/io_uring.c | 6 ++++++
include/linux/uio.h | 5 ++++-
2 files changed, 10 insertions(+), 1 deletion(-)
--
2.32.0
next reply other threads:[~2021-08-09 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 11:52 Pavel Begunkov [this message]
2021-08-09 11:52 ` [PATCH 1/2] iov_iter: mark truncated iters Pavel Begunkov
2021-08-09 11:52 ` [PATCH 2/2] io_uring: don't retry with truncated iter Pavel Begunkov
2021-08-09 15:52 ` [PATCH 0/2] iter revert problems Al Viro
2021-08-09 18:56 ` Pavel Begunkov
2021-08-10 8:47 ` David Laight
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] \
[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