From: David Hildenbrand <david@redhat.com>
To: Yang Shi <shy828301@gmail.com>, Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, David Howells <dhowells@redhat.com>
Subject: Re: Can the huge zero page be partially mapped?
Date: Mon, 4 Mar 2024 22:52:44 +0100 [thread overview]
Message-ID: <5b421e91-79ed-4be7-bf03-c34ef9a674d0@redhat.com> (raw)
In-Reply-To: <CAHbLzkpjWvBDqFzz1hysnmQRMzEE9vc4fyQDO2CJX8Om6ZpBsA@mail.gmail.com>
On 04.03.24 20:19, Yang Shi wrote:
> On Mon, Mar 4, 2024 at 8:54 AM Matthew Wilcox <willy@infradead.org> wrote:
>>
>> I looked at the definition of is_huge_zero_page():
>>
>> static inline bool is_huge_zero_page(struct page *page)
>> {
>> return READ_ONCE(huge_zero_page) == page;
>> }
>>
>> That made me raise my eyebrows a bit because it will return false for
>> tail pages of the HZP (that was at least unexpected for me). Then we
>> have this beauty:
>>
>> void free_page_and_swap_cache(struct page *page)
>> {
>> struct folio *folio = page_folio(page);
>>
>> free_swap_cache(folio);
>> if (!is_huge_zero_page(page))
>> folio_put(folio);
>> }
>>
>> So if we can call free_page_and_swap_cache() with a tail of the HZP
>> we can absolutely screw up its refcounting. Now, we have VM_BUGs
>> to catch the refcount going below 0, and I haven't seen them being
>> hit, so I _presume_ it doesn't happen, but maybe somebody inventive
>> could come up with a way of putting a HZP tail into a page table ...?
>
> The huge zero pmd split is specially handled by
> __split_huge_zero_page_pmd(), which actually replaces every subpages
> of HZP to zero page.
Right.
The only thing that can happen is that we GUP a part of the huge
zeropage (FOLL_PIN only, FOLL_LONGTERM/FOLL_WRITE would trigger a fault
first and map us an anon folio), and unpinning would drop these references.
unpin_user_page()->gup_put_folio()->folio_put_refs() would call
__folio_put().
Not sure if __folio_put() does the right thing, but I hope so :) Did not
look into the details.
In folios_put_refs() we do have is_huge_zero_page() special handling, I
guess that is for ordinary zap/unmap and likely the right thing to do.
Looks a bit inconsistent. (folio_put_refs() vs. folios_put_refs())
Likely, we should also not perform any refcounting on the huge zeropage
in GUP, just like we do for the ordinary zeropage nowdays. [ccing Dave]
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-03-04 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 16:54 Matthew Wilcox
2024-03-04 19:19 ` Yang Shi
2024-03-04 21:52 ` 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=5b421e91-79ed-4be7-bf03-c34ef9a674d0@redhat.com \
--to=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-mm@kvack.org \
--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