[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250219155212.9474b8c44bd58780a54c8a6e@linux-foundation.org>
Date: Wed, 19 Feb 2025 15:52:12 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Luiz Capitulino <luizcap@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, david@...hat.com,
yuzhao@...gle.com, pasha.tatashin@...een.com, hannes@...xchg.org,
muchun.song@...ux.dev
Subject: Re: [PATCH 0/4] mm: page_ext: Introduce new iteration API
On Tue, 18 Feb 2025 21:17:46 -0500 Luiz Capitulino <luizcap@...hat.com> 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?
Powered by blists - more mailing lists