From: Jens Axboe <axboe@kernel.dk>
To: linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Kent Overstreet <kent.overstreet@gmail.com>
Subject: [PATCH] mm: mark async iocb read as NOWAIT once some data has been, copied
Date: Sat, 17 Oct 2020 09:30:59 -0600 [thread overview]
Message-ID: <59eae433-9b30-f094-534d-eb5cf0a40a80@kernel.dk> (raw)
Once we've copied some data for an iocb that is marked with IOCB_WAITQ,
we should no longer attempt to async lock a new page. Instead make sure
we return the copied amount, and let the caller retry, instead of
returning -EIOCBQUEUED for a new page.
This should only be possible with read-ahead disabled on the below
device, and multiple threads racing on the same file. Haven't been able
to reproduce on anything else.
Cc: stable@vger.kernel.org # v5.9
Fixes: 1a0a7853b901 ("mm: support async buffered reads in generic_file_buffered_read()")
Reported-by: Kent Overstreet <kent.overstreet@gmail.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
---
mm/filemap.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/mm/filemap.c b/mm/filemap.c
index 1a6beaf69f49..029787fda56b 100644
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -2185,6 +2185,7 @@ ssize_t generic_file_buffered_read(struct kiocb *iocb,
pgoff_t index;
pgoff_t last_index;
pgoff_t prev_index;
+ ssize_t this_written = 0;
unsigned long offset; /* offset into pagecache page */
unsigned int prev_offset;
int error = 0;
@@ -2207,6 +2208,14 @@ ssize_t generic_file_buffered_read(struct kiocb *iocb,
cond_resched();
find_page:
+ /*
+ * If we've already successfully copied some data, then we
+ * can no longer safely return -EIOCBQUEUED. Hence mark
+ * an async read NOWAIT at that point.
+ */
+ if (this_written && (iocb->ki_flags & IOCB_WAITQ))
+ iocb->ki_flags |= IOCB_NOWAIT;
+
if (fatal_signal_pending(current)) {
error = -EINTR;
goto out;
@@ -2239,7 +2248,7 @@ ssize_t generic_file_buffered_read(struct kiocb *iocb,
* serialisations and why it's safe.
*/
if (iocb->ki_flags & IOCB_WAITQ) {
- if (written) {
+ if (this_written) {
put_page(page);
goto out;
}
@@ -2328,7 +2337,7 @@ ssize_t generic_file_buffered_read(struct kiocb *iocb,
prev_offset = offset;
put_page(page);
- written += ret;
+ this_written += ret;
if (!iov_iter_count(iter))
goto out;
if (ret < nr) {
@@ -2448,6 +2457,7 @@ ssize_t generic_file_buffered_read(struct kiocb *iocb,
*ppos = ((loff_t)index << PAGE_SHIFT) + offset;
file_accessed(filp);
+ written += this_written;
return written ? written : error;
}
EXPORT_SYMBOL_GPL(generic_file_buffered_read);
--
2.28.0
--
Jens Axboe
next reply other threads:[~2020-10-17 15:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 15:30 Jens Axboe [this message]
2020-10-17 16:28 ` Matthew Wilcox
2020-10-17 17:30 ` Jens Axboe
2020-10-17 19:13 ` Kent Overstreet
2020-10-17 19: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 \
--in-reply-to=59eae433-9b30-f094-534d-eb5cf0a40a80@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-mm@kvack.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