[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9bd4f53c-fba4-f0f5-68d1-4b2acaab4213@huawei.com>
Date: Fri, 18 Mar 2022 14:29:15 +0800
From: Miaohe Lin <linmiaohe@...wei.com>
To: David Hildenbrand <david@...hat.com>
CC: <linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>,
<akpm@...ux-foundation.org>, <naoya.horiguchi@....com>,
<shy828301@...il.com>, <mike.kravetz@...cle.com>
Subject: Re: [PATCH v3 1/2] mm/memory-failure.c: avoid calling
invalidate_inode_page() with unexpected pages
On 2022/3/17 20:29, David Hildenbrand wrote:
> On 18.03.22 08:39, 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.
>>
>> Signed-off-by: Miaohe Lin <linmiaohe@...wei.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.
>
> I'm not familiar with this code to ack this, but it looks sane to me.
>
Thanks David.
Powered by blists - more mailing lists