[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <829c4d81-7693-4f41-b518-aafd6dcb4984@redhat.com>
Date: Tue, 11 Feb 2025 16:09:58 +0100
From: David Hildenbrand <david@...hat.com>
To: Luiz Capitulino <luizcap@...hat.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, yuzhao@...gle.com
Cc: akpm@...ux-foundation.org, hannes@...xchg.org, muchun.song@...ux.dev,
lcapitulino@...il.com
Subject: Re: [RFC 3/4] mm: page_table_check: use new iteration API
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@...hat.com>
> ---
The usage of the new API here looks straight forward here. The
page_owner one is a bit more involved :)
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists