From: David Hildenbrand <david@redhat.com>
To: Luiz Capitulino <luizcap@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
yuzhao@google.com
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
muchun.song@linux.dev, lcapitulino@gmail.com
Subject: Re: [RFC 3/4] mm: page_table_check: use new iteration API
Date: Tue, 11 Feb 2025 16:09:58 +0100 [thread overview]
Message-ID: <829c4d81-7693-4f41-b518-aafd6dcb4984@redhat.com> (raw)
In-Reply-To: <1a661d3c94890df06dc82583f883ee5cc6346d75.1737754625.git.luizcap@redhat.com>
On 24.01.25 22:37, 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 page_ext_iter API
> instead.
>
> Fixes: e98337d11bbd ("mm/contig_alloc: support __GFP_COMP")
> Signed-off-by: Luiz Capitulino <luizcap@redhat.com>
> ---
The usage of the new API here looks straight forward here. The
page_owner one is a bit more involved :)
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-02-11 15:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 21:37 [RFC 0/4] mm: page_ext: Fix crash when reserving 1G pages Luiz Capitulino
2025-01-24 21:37 ` [RFC 1/4] mm: page_ext: add an iteration API for page extensions Luiz Capitulino
2025-02-11 15:25 ` David Hildenbrand
2025-02-11 16:07 ` Luiz Capitulino
2025-01-24 21:37 ` [RFC 2/4] mm: page_owner: use new iteration API Luiz Capitulino
2025-02-11 15:15 ` David Hildenbrand
2025-02-11 16:00 ` Luiz Capitulino
2025-01-24 21:37 ` [RFC 3/4] mm: page_table_check: " Luiz Capitulino
2025-02-11 15:09 ` David Hildenbrand [this message]
2025-01-24 21:37 ` [RFC 4/4] mm: page_ext: drop page_ext_next() 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=829c4d81-7693-4f41-b518-aafd6dcb4984@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=lcapitulino@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luizcap@redhat.com \
--cc=muchun.song@linux.dev \
--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