From: Axel Rasmussen <axelrasmussen@google.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Revert "ptdesc: remove references to folios from __pagetable_ctor() and pagetable_dtor()"
Date: Wed, 25 Feb 2026 13:50:45 -0800 [thread overview]
Message-ID: <CAJHvVcjnSc16wtYrCt8i+UFUmGzoAwKXoB8CGMLwz4NEG32QnQ@mail.gmail.com> (raw)
In-Reply-To: <aZ9OEAzENzeFYDB2@cmpxchg.org>
On Wed, Feb 25, 2026 at 11:31 AM Johannes Weiner <hannes@cmpxchg.org> wrote:
>
> On Tue, Feb 24, 2026 at 04:24:34PM -0800, Axel Rasmussen wrote:
> > This change swapped out mod_node_page_state for lruvec_stat_add_folio.
> > But, these two APIs are not interchangeable: the lruvec version also
> > increments memcg stats, in addition to "global" pgdat stats.
> >
> > So after this change, the "pagetables" memcg stat in memory.stat always
> > yields "0", which is a userspace visible regression.
> >
> > I tried to look for a refactor where we add a variant of
> > lruvec_stat_mod_folio which takes a pgdat and a memcg instead of a
> > folio, to try to adhere to the spirit of the original patch. But at the
> > end of the day this just means we have to call
> > folio_memcg(ptdesc_folio(ptdesc)) anyway, which doesn't really
> > accomplish much.
> >
> > This regression is visible in master as well as 6.18 stable, so CC
> > stable too.
> >
> > Fixes: f0c92726e89f ("ptdesc: remove references to folios from __pagetable_ctor() and pagetable_dtor()")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Axel Rasmussen <axelrasmussen@google.com>
>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
>
> Willy's cleanup proposal looks good to me too, but this is more
> straight forward to backport to stable.
Thanks all for taking a look! I feel similarly, the other series looks
reasonable (modulo a couple of fixups pointed out in the other
thread), but at least for 6.18 / stable I would mildly prefer to just
do the simpler thing and put the status quo back. (Especially since
the other approach needs a bit more tweaking.)
next prev parent reply other threads:[~2026-02-25 21:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 0:24 Axel Rasmussen
2026-02-25 16:03 ` Matthew Wilcox
2026-02-25 16:05 ` Matthew Wilcox
2026-02-25 16:08 ` David Hildenbrand (Arm)
2026-02-25 17:06 ` Shakeel Butt
2026-02-25 16:04 ` David Hildenbrand (Arm)
2026-02-25 16:06 ` David Hildenbrand (Arm)
2026-02-25 17:18 ` Shakeel Butt
2026-02-25 19:31 ` Johannes Weiner
2026-02-25 21:50 ` Axel Rasmussen [this message]
2026-02-25 22:11 ` Vishal Moola (Oracle)
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=CAJHvVcjnSc16wtYrCt8i+UFUmGzoAwKXoB8CGMLwz4NEG32QnQ@mail.gmail.com \
--to=axelrasmussen@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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