From: David Hildenbrand <david@redhat.com>
To: Luiz Capitulino <luizcap@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
yuzhao@google.com, pasha.tatashin@soleen.com
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, muchun.song@linux.dev
Subject: Re: [PATCH 2/4] mm: page_table_check: use new iteration API
Date: Thu, 20 Feb 2025 12:05:23 +0100 [thread overview]
Message-ID: <fdef74f3-ada8-40c7-afea-9a0105f5c05f@redhat.com> (raw)
In-Reply-To: <85f11743d259d5e4a1f47456fbcda82ff6db9ab3.1739931468.git.luizcap@redhat.com>
On 19.02.25 03:17, Luiz Capitulino wrote:
> The page_ext_next() function assumes that page extension objects for a
> page order allocation always reside in the same memory section, which
> may not be true and could lead to crashes. Use the new page_ext
> iteration API instead.
>
> Fixes: cf54f310d0d3 ("mm/hugetlb: use __GFP_COMP for gigantic folios")
> Signed-off-by: Luiz Capitulino <luizcap@redhat.com>
> ---
> mm/page_table_check.c | 39 ++++++++++++---------------------------
> 1 file changed, 12 insertions(+), 27 deletions(-)
>
> diff --git a/mm/page_table_check.c b/mm/page_table_check.c
> index 509c6ef8de400..b52e04d31c809 100644
> --- a/mm/page_table_check.c
> +++ b/mm/page_table_check.c
> @@ -62,24 +62,20 @@ static struct page_table_check *get_page_table_check(struct page_ext *page_ext)
> */
> static void page_table_check_clear(unsigned long pfn, unsigned long pgcnt)
> {
> + struct page_ext_iter iter;
> struct page_ext *page_ext;
> struct page *page;
> - unsigned long i;
> bool anon;
>
> if (!pfn_valid(pfn))
> return;
>
> page = pfn_to_page(pfn);
> - page_ext = page_ext_get(page);
> -
> - if (!page_ext)
> - return;
> -
> BUG_ON(PageSlab(page));
> anon = PageAnon(page);
>
> - for (i = 0; i < pgcnt; i++) {
> + rcu_read_lock();
> + for_each_page_ext(page, pgcnt, page_ext, iter) {
> struct page_table_check *ptc = get_page_table_check(page_ext);
>
> if (anon) {
> @@ -89,9 +85,8 @@ static void page_table_check_clear(unsigned long pfn, unsigned long pgcnt)
> BUG_ON(atomic_read(&ptc->anon_map_count));
> BUG_ON(atomic_dec_return(&ptc->file_map_count) < 0);
> }
> - page_ext = page_ext_next(page_ext);
> }
> - page_ext_put(page_ext);
> + rcu_read_unlock();
> }
[...]
>
> /*
> @@ -140,24 +130,19 @@ static void page_table_check_set(unsigned long pfn, unsigned long pgcnt,
> */
> void __page_table_check_zero(struct page *page, unsigned int order)
> {
> + struct page_ext_iter iter;
> struct page_ext *page_ext;
> - unsigned long i;
>
> BUG_ON(PageSlab(page));
>
> - page_ext = page_ext_get(page);
> -
> - if (!page_ext)
> - return;
> -
> - for (i = 0; i < (1ul << order); i++) {
> + rcu_read_lock();
> + for_each_page_ext_order(page, order, page_ext, iter) {
I would avoid introducing for_each_page_ext_order() and just pass "1 <<
order" as the page count.
> struct page_table_check *ptc = get_page_table_check(page_ext);
>
> BUG_ON(atomic_read(&ptc->anon_map_count));
> BUG_ON(atomic_read(&ptc->file_map_count));
> - page_ext = page_ext_next(page_ext);
> }
> - page_ext_put(page_ext);
> + rcu_read_unlock();
> }
>
> void __page_table_check_pte_clear(struct mm_struct *mm, pte_t pte)
Apart from that, this looks very nice to me
Acked-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-02-20 11:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 2:17 [PATCH 0/4] mm: page_ext: Introduce " Luiz Capitulino
2025-02-19 2:17 ` [PATCH 1/4] mm: page_ext: add an iteration API for page extensions Luiz Capitulino
2025-02-20 10:59 ` David Hildenbrand
2025-02-20 20:36 ` Luiz Capitulino
2025-02-20 20:45 ` David Hildenbrand
2025-02-20 20:47 ` David Hildenbrand
2025-02-20 21:12 ` Luiz Capitulino
2025-02-19 2:17 ` [PATCH 2/4] mm: page_table_check: use new iteration API Luiz Capitulino
2025-02-20 11:05 ` David Hildenbrand [this message]
2025-02-20 20:37 ` Luiz Capitulino
2025-02-19 2:17 ` [PATCH 3/4] mm: page_owner: " Luiz Capitulino
2025-02-19 2:17 ` [PATCH 4/4] mm: page_ext: make page_ext_next() private to page_ext Luiz Capitulino
2025-02-19 23:52 ` [PATCH 0/4] mm: page_ext: Introduce new iteration API Andrew Morton
2025-02-20 10:49 ` David Hildenbrand
2025-02-20 20:23 ` Luiz Capitulino
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=fdef74f3-ada8-40c7-afea-9a0105f5c05f@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luizcap@redhat.com \
--cc=muchun.song@linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=yuzhao@google.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