From: Matthew Wilcox <willy@infradead.org>
To: coolqyj@163.com
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
Qian Yingjin <qian@ddn.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] [PATCH V2] mm/filemap: fix page end in filemap_get_read_batch
Date: Wed, 8 Feb 2023 02:28:50 +0000 [thread overview]
Message-ID: <Y+MI4mdGfXYDcp0R@casper.infradead.org> (raw)
In-Reply-To: <20230208022400.28962-1-coolqyj@163.com>
On Wed, Feb 08, 2023 at 10:24:00AM +0800, coolqyj@163.com wrote:
> From: Qian Yingjin <qian@ddn.com>
>
> I was running traces of the read code against an RAID storage
> system to understand why read requests were being misaligned
> against the underlying RAID strips. I found that the page end
> offset calculation in filemap_get_read_batch() was off by one.
>
> When a read is submitted with end offset 1048575, then it
> calculates the end page for read of 256 when it should be 255.
> "last_index" is the index of the page beyond the end of the read
> and it should be skipped when get a batch of pages for read in
> @filemap_get_read_batch().
>
> The below simple patch fixes the problem. This code was introduced
> in kernel 5.12.
>
> Fixes: cbd59c48ae2b ("mm/filemap: use head pages in generic_file_buffered_read")
> Signed-off-by: Qian Yingjin <qian@ddn.com>
Reviewed-by: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: stable@vger.kernel.org
> ---
> mm/filemap.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/mm/filemap.c b/mm/filemap.c
> index c4d4ace9cc70..0e20a8d6dd93 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -2588,18 +2588,19 @@ static int filemap_get_pages(struct kiocb *iocb, struct iov_iter *iter,
> struct folio *folio;
> int err = 0;
>
> + /* "last_index" is the index of the page beyond the end of the read */
> last_index = DIV_ROUND_UP(iocb->ki_pos + iter->count, PAGE_SIZE);
> retry:
> if (fatal_signal_pending(current))
> return -EINTR;
>
> - filemap_get_read_batch(mapping, index, last_index, fbatch);
> + filemap_get_read_batch(mapping, index, last_index - 1, fbatch);
> if (!folio_batch_count(fbatch)) {
> if (iocb->ki_flags & IOCB_NOIO)
> return -EAGAIN;
> page_cache_sync_readahead(mapping, ra, filp, index,
> last_index - index);
> - filemap_get_read_batch(mapping, index, last_index, fbatch);
> + filemap_get_read_batch(mapping, index, last_index - 1, fbatch);
> }
> if (!folio_batch_count(fbatch)) {
> if (iocb->ki_flags & (IOCB_NOWAIT | IOCB_WAITQ))
> --
> 2.34.1
>
parent reply other threads:[~2023-02-08 2:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230208022400.28962-1-coolqyj@163.com>]
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=Y+MI4mdGfXYDcp0R@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=coolqyj@163.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qian@ddn.com \
/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