Re: [RFC 3/4] mm: page_table_check: use new iteration API

[David Hildenbrand]

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@xxxxxxxxxx>
> ---

The usage of the new API here looks straight forward here. The 
page_owner one is a bit more involved :)

--
Cheers,

David / dhildenb