From: David Hildenbrand <david@redhat.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Oscar Salvador <osalvador@suse.de>,
Miaohe Lin <linmiaohe@huawei.com>
Subject: Re: [PATCH 1/2] mm: Turn folio_test_hugetlb into a PageType
Date: Thu, 14 Mar 2024 11:26:17 +0100 [thread overview]
Message-ID: <b414424c-52fd-439e-ab5b-96d43199516b@redhat.com> (raw)
In-Reply-To: <20240314012506.1600378-2-willy@infradead.org>
On 14.03.24 02:25, Matthew Wilcox (Oracle) wrote:
> The current folio_test_hugetlb() can be fooled by a concurrent folio split
> into returning true for a folio which has never belonged to hugetlbfs.
> This can't happen if the caller holds a refcount on it, but we have a
> few places (memory-failure, compaction, procfs) which do not and should
> not take a speculative reference.
>
> Since hugetlb pages do not use individual page mapcounts (they are always
> fully mapped and use the entire_mapcount field to record the number of
> mappings), the PageType field is available for use with only a minor
> modification to page_mapcount() to ignore the value in this field for
> hugetlb pages. Other parts of the kernel which examine page->_mapcount
> directly already know about page_has_type() (eg procfs, dump_page()).
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> ---
Should we include this hunk:
diff --git a/mm/debug.c b/mm/debug.c
index c1c1a6a484e4c..f521e17150a10 100644
--- a/mm/debug.c
+++ b/mm/debug.c
@@ -63,7 +63,8 @@ static void __dump_folio(struct folio *folio, struct page *page,
* encode own info, and we must avoid calling page_folio() again.
*/
if (!folio_test_slab(folio)) {
- mapcount = atomic_read(&page->_mapcount) + 1;
+ if (!folio_test_hugetlb(folio))
+ mapcount = atomic_read(&page->_mapcount) + 1;
if (folio_test_large(folio))
mapcount += folio_entire_mapcount(folio);
}
Apart from that, LGTM
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-03-14 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 1:25 [PATCH 0/2] Reliable testing for hugetlb Matthew Wilcox (Oracle)
2024-03-14 1:25 ` [PATCH 1/2] mm: Turn folio_test_hugetlb into a PageType Matthew Wilcox (Oracle)
2024-03-14 10:26 ` David Hildenbrand [this message]
2024-03-14 14:33 ` Matthew Wilcox
2024-03-15 6:19 ` Miaohe Lin
2024-03-15 12:32 ` Matthew Wilcox
2024-03-18 1:45 ` Miaohe Lin
2024-03-14 1:25 ` [PATCH 2/2] mm: Remove a call to compound_head() from is_page_hwpoison() Matthew Wilcox (Oracle)
2024-03-14 10:26 ` David Hildenbrand
2024-03-15 6:38 ` 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=b414424c-52fd-439e-ab5b-96d43199516b@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--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).