linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Kucharski <william.kucharski@oracle.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Miklos Szeredi <mszeredi@redhat.com>
Subject: Re: [PATCH] mm/filemap: Drop check for truncated page after I/O
Date: Thu, 4 Mar 2021 22:50:45 +0000	[thread overview]
Message-ID: <4BF4F395-B102-4FAE-9AD9-9EDE93F5E6FB@oracle.com> (raw)
In-Reply-To: <20210303222547.1056428-1-willy@infradead.org>

LGTM.

Reviewed-by: William Kucharski <william.kucharski@oracle.com>

> On Mar 3, 2021, at 3:25 PM, Matthew Wilcox (Oracle) <willy@infradead.org> wrote:
> 
> If the I/O completed successfully, the page will remain Uptodate,
> even if it is subsequently truncated.  If the I/O completed with an error,
> this check would cause us to retry the I/O if the page were truncated
> before we woke up.  There is no need to retry the I/O; the I/O to fill
> the page failed, so we can legitimately just return -EIO.
> 
> This code was originally added by commit 56f0d5fe6851 ("[PATCH]
> readpage-vs-invalidate fix") in 2005 (this commit ID is from the
> linux-fullhistory tree; it is also commit ba1f08f14b52 in tglx-history).
> 
> At the time, truncate_complete_page() called ClearPageUptodate(), and
> so this was fixing a real bug.  In 2008, commit 84209e02de48
> ("mm: dont clear PG_uptodate on truncate/invalidate") removed the
> call to ClearPageUptodate, and this check has been unnecessary ever
> since.
> 
> It doesn't do any real harm, but there's no need to keep it.
> 
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> ---
> mm/filemap.c | 2 --
> 1 file changed, 2 deletions(-)
> 
> diff --git a/mm/filemap.c b/mm/filemap.c
> index 8d3e0daed7c9..3d1635d3be3e 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -2238,8 +2238,6 @@ static int filemap_read_page(struct file *file, struct address_space *mapping,
> 		return error;
> 	if (PageUptodate(page))
> 		return 0;
> -	if (!page->mapping)	/* page truncated */
> -		return AOP_TRUNCATED_PAGE;
> 	shrink_readahead_size_eio(&file->f_ra);
> 	return -EIO;
> }
> -- 
> 2.30.0
> 
> 


      reply	other threads:[~2021-03-04 22:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 22:25 [PATCH] mm/filemap: Drop check for truncated page after I/O Matthew Wilcox (Oracle)
2021-03-04 22:50 ` William Kucharski [this message]

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=4BF4F395-B102-4FAE-9AD9-9EDE93F5E6FB@oracle.com \
    --to=william.kucharski@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mszeredi@redhat.com \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).