From: David Hildenbrand <david@redhat.com>
To: James Houghton <jthoughton@google.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-mm@kvack.org, Naoya Horiguchi <naoya.horiguchi@linux.dev>,
David Rientjes <rientjes@google.com>,
Michal Hocko <mhocko@suse.com>,
Matthew Wilcox <willy@infradead.org>,
Peter Xu <peterx@redhat.com>,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: A mapcount riddle
Date: Thu, 26 Jan 2023 10:10:55 +0100 [thread overview]
Message-ID: <6e9b29af-b6e8-77c3-edec-d1713b76ce89@redhat.com> (raw)
In-Reply-To: <CADrL8HXRihom3xbhF=ZqRy2a9o54oLR2dFsmeHWF95j0FGKa9g@mail.gmail.com>
On 25.01.23 16:26, James Houghton wrote:
>> At first thought this seems bad. However, I believe this has been the
>> behavior since hugetlb PMD sharing was introduced in 2006 and I am
>> unaware of any reported issues. I did a audit of code looking at
>> mapcount. In addition to the above issue with smaps, there appears
>> to be an issue with 'migrate_pages' where shared pages could be migrated
>> without appropriate privilege.
>>
>> /* With MPOL_MF_MOVE, we migrate only unshared hugepage. */
>> if (flags & (MPOL_MF_MOVE_ALL) ||
>> (flags & MPOL_MF_MOVE && page_mapcount(page) == 1)) {
>> if (isolate_hugetlb(page, qp->pagelist) &&
>> (flags & MPOL_MF_STRICT))
>> /*
>> * Failed to isolate page but allow migrating pages
>> * which have been queued.
>> */
>> ret = 1;
>> }
>
> This isn't the exact same problem you're fixing Mike, but I want to
> point out a related problem.
>
> This is the generic-mm-equivalent of the hugetlb code above:
>
> static int migrate_page_add(struct page *page, struct list_head
> *pagelist, unsigned long flags)
> {
> struct page *head = compound_head(page);
> /*
> * Avoid migrating a page that is shared with others.
> */
> if ((flags & MPOL_MF_MOVE_ALL) || page_mapcount(head) == 1) {
> if (!isolate_lru_page(head)) {
> list_add_tail(&head->lru, pagelist);
> mod_node_page_state(page_pgdat(head),
> NR_ISOLATED_ANON + page_is_file_lru(head),
> thp_nr_pages(head));
> ...
> }
>
> If you have a partially PTE-mapped THP, page_mapcount(head) will not
> accurately determine if a page is mapped in multiple VMAs or not (it
> only tells you how many times the head page is mapped).
This came up in the context of [1]. As the new naming (and my naming
change) suggestion implies, this is a pure estimate of the numbers of
sharers. The check is not supposed to be accurate and it can't be.
[1] https://lkml.kernel.org/r/20230124012210.13963-1-vishal.moola@gmail.com
>
> For example...
> 1) You could have the THP PMD-mapped in one VMA, and then one tail
> page of the THP can be mapped in another. page_mapcount(head) will be
> 1.
> 2) You could have two VMAs map two separate tail pages of the THP, in
> which case page_mapcount(head) will be 0.
>
> I bring this up because we have the same problem with HugeTLB
> high-granularity mapping.
The more I think of it, the nicer it would be to just keep maintaining a
single mapcount+ref for the hugetlb case ...
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2023-01-26 9:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 20:56 A mapcount riddle Mike Kravetz
2023-01-24 23:00 ` Peter Xu
2023-01-24 23:29 ` Yang Shi
2023-01-25 16:02 ` Peter Xu
2023-01-25 18:26 ` Yang Shi
2023-01-24 23:35 ` Mike Kravetz
2023-01-25 16:46 ` Peter Xu
2023-01-25 18:16 ` Mike Kravetz
2023-01-25 20:13 ` Peter Xu
2023-01-25 8:24 ` Michal Hocko
2023-01-25 17:59 ` Mike Kravetz
2023-01-26 9:16 ` Michal Hocko
2023-01-26 17:51 ` Mike Kravetz
2023-01-27 9:56 ` Michal Hocko
2023-01-25 9:09 ` David Hildenbrand
2023-01-25 15:26 ` James Houghton
2023-01-25 15:54 ` Peter Xu
2023-01-25 16:22 ` James Houghton
2023-01-25 19:26 ` Vishal Moola
2023-01-26 9:15 ` David Hildenbrand
2023-01-26 18:22 ` Yang Shi
2023-01-26 9:10 ` David Hildenbrand [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=6e9b29af-b6e8-77c3-edec-d1713b76ce89@redhat.com \
--to=david@redhat.com \
--cc=jthoughton@google.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@linux.dev \
--cc=peterx@redhat.com \
--cc=rientjes@google.com \
--cc=songmuchun@bytedance.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).