mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: <akpm@linux-foundation.org>, <naoya.horiguchi@nec.com>,
	<shy828301@gmail.com>, <mike.kravetz@oracle.com>,
	<david@redhat.com>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] mm/memory-failure.c: avoid calling invalidate_inode_page() with unexpected pages
Date: Mon, 21 Mar 2022 10:18:01 +0800	[thread overview]
Message-ID: <0d5f2c97-992b-442c-9ecf-26ba363461aa@huawei.com> (raw)
In-Reply-To: <YjYC1XaeDPosSIDa@casper.infradead.org>

On 2022/3/20 0:20, Matthew Wilcox wrote:
> On Sun, Mar 20, 2022 at 01:13:33PM +0800, Miaohe Lin wrote:
>> invalidate_inode_page() can invalidate the pages in the swap cache because
>> the check of page->mapping != mapping is removed via Matthew's patch titled
>> "mm/truncate: Inline invalidate_complete_page() into its one caller". But
>> invalidate_inode_page() is not expected to deal with the pages in the swap
>> cache. Also non-lru movable page can reach here too. They're not page cache
>> pages. Skip these pages by checking PageSwapCache and PageLRU to fix this
>> unexpected issue.
> 
> I disagree with this changelog.
> 
> invalidate_inode_page() should not be called for pages which are not
> in the page cache.
>
> And then the patch shouldn't test PageLRU (which is actually wrong) or
> PageSwapCache().  It should simply be:
> > +	if (!PageHuge(page) && !PageAnon(page))

If we reach here, the page can be one of the PageHuge, __PageMovable and PageLRU.
If above code is used, __PageMovable can pass the check and enter the invalidate_inode_page
unexpectedly. So I think PageLRU check is necessary here. But it seems PageSwapCache
is only reliable when PageAnon, so might we should do:

+	if (!PageHuge(page) && PageLRU(page) && !PageAnon(page))

Am I miss something? Many thanks for comment.

> 
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>>  mm/memory-failure.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>> index 5444a8ef4867..ecf45961f3b6 100644
>> --- a/mm/memory-failure.c
>> +++ b/mm/memory-failure.c
>> @@ -2178,7 +2178,7 @@ static int __soft_offline_page(struct page *page)
>>  		return 0;
>>  	}
>>  
>> -	if (!PageHuge(page))
>> +	if (!PageHuge(page) && PageLRU(page) && !PageSwapCache(page))
>>  		/*
>>  		 * Try to invalidate first. This should work for
>>  		 * non dirty unmapped page cache pages.
>> -- 
>> 2.23.0
>>
>>
> 
> .
> 


  reply	other threads:[~2022-03-21  2:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-20  5:13 [PATCH v4 0/2] A few fixup patches for memory failure Miaohe Lin
2022-03-20  5:13 ` [PATCH v4 1/2] mm/memory-failure.c: avoid calling invalidate_inode_page() with unexpected pages Miaohe Lin
2022-03-19 16:20   ` Matthew Wilcox
2022-03-21  2:18     ` Miaohe Lin [this message]
2022-03-20  5:13 ` [PATCH v4 2/2] mm/memory-failure.c: make non-LRU movable pages unhandlable Miaohe Lin

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=0d5f2c97-992b-442c-9ecf-26ba363461aa@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=naoya.horiguchi@nec.com \
    --cc=shy828301@gmail.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

all inboxes | Powered by JetHome®