From: David Hildenbrand <david@redhat.com>
To: "lixinhai.lxh@gmail.com" <lixinhai.lxh@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: akpm <akpm@linux-foundation.org>, mhocko <mhocko@suse.com>
Subject: Re: [PATCH] mm: Improve PageAnon() to check the whole PAGE_MAPPING_FLAGS
Date: Fri, 15 Nov 2019 13:50:38 +0100 [thread overview]
Message-ID: <da837c8b-ecf6-5ded-29a3-97d61f129daf@redhat.com> (raw)
In-Reply-To: <2019111513593472959835@gmail.com>
On 15.11.19 06:59, lixinhai.lxh@gmail.com wrote:
> On 2019-11-15 at 11:18 Li Xinhai wrote:
>> PageAnon() just checking on PAGE_MAPPING_ANON bit would cause page,
>> with PageKsm as true, been wrongly considered as PageAnon. Now,
>> checking the whole PAGE_MAPPING_FLAGS to avoid this error.
>>
>> Reported from:
>> https://lore.kernel.org/linux-mm/20191113000651.20677-1-rcampbell@nvidia.com/
>>
>> Reported-by: Ralph Campbell <rcampbell@nvidia.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Michal Hocko <mhocko@suse.com>
>> Signed-off-by: Li Xinhai <lixinhai.lxh@gmail.com>
>> ---
>> include/linux/page-flags.h | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/linux/page-flags.h b/include/linux/page-flags.h
>> index 1bf83c8..1849fc3 100644
>> --- a/include/linux/page-flags.h
>> +++ b/include/linux/page-flags.h
>> @@ -461,7 +461,8 @@ static __always_inline int PageMappingFlags(struct page *page)
>> static __always_inline int PageAnon(struct page *page)
>> {
>> page = compound_head(page);
>> - return ((unsigned long)page->mapping & PAGE_MAPPING_ANON) != 0;
>> + return ((unsigned long)page->mapping & PAGE_MAPPING_FLAGS) ==
>> + PAGE_MAPPING_ANON;
>> }
>>
>> static __always_inline int __PageMovable(struct page *page)
>> --
>> 1.8.3.1
>>
>
> The current semantics of PageAnon() for both KSM and !KSM are used in many
> places, so can't change it alone without change other code.
> Need skip this patch.
... I assume that was intended because KSM only merges anonymous pages?
If it was not intended, it would scream for a cleanup.
>
> - Xinhai
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-11-15 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 3:18 Li Xinhai
2019-11-15 5:59 ` lixinhai.lxh
2019-11-15 12:50 ` David Hildenbrand [this message]
2019-11-15 13:09 ` lixinhai.lxh
2019-11-15 13:25 ` Michal Hocko
2019-11-15 15:01 ` lixinhai.lxh
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=da837c8b-ecf6-5ded-29a3-97d61f129daf@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lixinhai.lxh@gmail.com \
--cc=mhocko@suse.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