On 20.02.25 00:52, Andrew Morton wrote:
On Tue, 18 Feb 2025 21:17:46 -0500 Luiz Capitulino <luizcap@xxxxxxxxxx> wrote:
To fix this, this series introduces a new iteration API for page extension
objects. The API checks if the next page extension object can be retrieved
from the current section or if it needs to look up for it in another
section.
...
A regression since 6.12, so we should backport the fix.
...
include/linux/page_ext.h | 67 +++++++++++++++++++++++++++++++++++++---
mm/page_ext.c | 48 ++++++++++++++++++++++++++++
mm/page_owner.c | 61 +++++++++++++++++-------------------
mm/page_table_check.c | 39 +++++++----------------
4 files changed, 152 insertions(+), 63 deletions(-)
That's a lot to backport!
Is there some quick-n-dirty fixup we can apply for the sake of -stable
kernels, then work on this long-term approach for future kernels?
I assume we could loop in
reset_page_owner()/page_table_check_free()/set_page_owner()/page_table_check_alloc().
Not-so-nice for upstream, maybe good-enough for stable. Still nasty :)
OTOH, we don't really expect a lot of conflicts.
--
Cheers,
David / dhildenb
