From: "Zi Yan" <ziy@nvidia.com>
To: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>,
"Gregory Price (Meta)" <gourry@gourry.net>, <linux-mm@kvack.org>
Cc: <linux-trace-kernel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-team@meta.com>,
<akpm@linux-foundation.org>, <david@kernel.org>, <ljs@kernel.org>,
<liam@infradead.org>, <rppt@kernel.org>, <surenb@google.com>,
<mhocko@suse.com>, <kasong@tencent.com>, <qi.zheng@linux.dev>,
<shakeel.butt@linux.dev>, <baohua@kernel.org>,
<axelrasmussen@google.com>, <yuanchu@google.com>,
<weixugc@google.com>, <baoquan.he@linux.dev>,
<baolin.wang@linux.alibaba.com>, <rientjes@google.com>,
<rostedt@goodmis.org>, <mhiramat@kernel.org>,
<mathieu.desnoyers@efficios.com>, <muchun.song@linux.dev>,
<osalvador@suse.de>, <joshua.hahnjy@gmail.com>,
<rakie.kim@sk.com>, <ying.huang@linux.alibaba.com>,
<brendan.jackman@linux.dev>, <hannes@cmpxchg.org>,
<bigeasy@linutronix.de>, <clrkwllms@kernel.org>,
<nathan@kernel.org>, <ndesaulniers@google.com>,
<morbo@google.com>, <justinstitt@google.com>,
<Bessel.Wang@huawei.com>, <jiang.liu@huawei.com>,
<mgorman@techsingularity.net>, <anshuman.khandual@arm.com>,
"Josef Bacik" <josef@toxicpanda.com>, <stable@vger.kernel.org>
Subject: Re: [PATCH v5 02/12] mm/page_alloc: keep the pagesets of an empty zone
Date: Tue, 03 Nov 2026 11:04:23 -0500 [thread overview]
Message-ID: <DMLPC0D7EWRW.EVYWUONVO18A@nvidia.com> (raw)
In-Reply-To: <489b668a-033c-4161-93e8-15d6b9b28b51@kernel.org>
On Tue Nov 3, 2026 at 9:57 AM EST, Vlastimil Babka (SUSE) wrote:
> On 11/1/26 21:07, Zi Yan wrote:
>> On Sat Oct 31, 2026 at 10:13 PM EDT, Gregory Price (Meta) wrote:
>>> From: Josef Bacik <josef@toxicpanda.com>
>>>
>>> When the last memory of a zone goes offline, zone_pcp_reset() frees
>>> zone->per_cpu_pageset and zone->per_cpu_zonestats. Nothing waits for those
>>> who found the zone populated and still use the two pointers. They take
>>> neither the memory hotplug lock nor any other lock which offline_pages()
>>> holds, and some of them can sleep:
>>>
>>> CPU0 vmstat_update() CPU1 offline_pages()
>>> refresh_cpu_vm_stats()
>>> for_each_populated_zone(zone)
>>> pcp = zone->per_cpu_pageset
>>> cond_resched()
>>> adjust_present_page_count()
>>> zone_pcp_reset(zone)
>>> free_percpu(zone->per_cpu_pageset)
>>> decay_pcp_high(zone, pcp)
>>> __this_cpu_write(pcp->expire, 0)
>>>
>>> The same goes for drain_all_pages(NULL), which takes pcp->lock, for
>>> zone_pcp_update(), show_free_areas() and the readers and writers of the
>>> zonestats. If the per-cpu memory has got a new owner in the meantime, it
>>> is corrupted.
>>>
>>> The pagesets are only freed because setup_zone_pageset() would otherwise
>>> leak them when the zone gets memory again. Keep them instead and let
>>> setup_zone_pageset() and zone_pcp_init() use them again, like it is done
>>> with pgdat->per_cpu_nodestats. Their lists are empty, and their limits
>>> have been calculated for a zone without memory by the
>>> init_per_zone_wmark_min() of offline_pages(), which is what
>>> setup_zone_pageset() would come up with as well.
>>>
>>> Fixes: 340175b7d14d ("mm/hotplug: free zone->pageset when a zone becomes empty")
>>> Cc: <stable@vger.kernel.org>
>>> Assisted-by: LLM
>>> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
>>> Signed-off-by: David Hildenbrand (Arm) <david@kernel.org>
>>> Reviewed-by: Johannes Weiner <hannes@cmpxchg.org>
>>> Signed-off-by: Vlastimil Babka (SUSE) <vbabka@kernel.org>
>>> Signed-off-by: Gregory Price (Meta) <gourry@gourry.net>
>>> ---
>>> mm/page_alloc.c | 20 ++++++++++++++------
>>> 1 file changed, 14 insertions(+), 6 deletions(-)
>>
>> LGTM. Just a nit below:
>>
>> Reviewed-by: Zi Yan <ziy@nvidia.com>
>>
>>>
>>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>>> index f1048168c90c..1850a41f24f7 100644
>>> --- a/mm/page_alloc.c
>>> +++ b/mm/page_alloc.c
>>> @@ -6308,6 +6308,10 @@ void __meminit setup_zone_pageset(struct zone *zone)
>>> {
>>> int cpu;
>>>
>>> + /* The zone has been populated before, see zone_pcp_reset(). */
>>> + if (zone->per_cpu_pageset != &boot_pageset)
>>> + return;
>>> +
>>> /* Size may be 0 on !SMP && !NUMA */
>>> if (sizeof(struct per_cpu_zonestat) > 0)
>>> zone->per_cpu_zonestats = alloc_percpu(struct per_cpu_zonestat);
>>> @@ -6400,6 +6404,10 @@ void __init setup_per_cpu_pageset(void)
>>>
>>> __meminit void zone_pcp_init(struct zone *zone)
>>> {
>>> + /* A node which is added again, see zone_pcp_reset(). */
>>
>> it might be better to explain zone->per_cpu_pageset can only be NULL at
>> boot time and it needs an initialization.
>
> Hmm.
>
>>> + if (zone->per_cpu_pageset && zone->per_cpu_pageset != &boot_pageset)
>>> + return;
>
> Shouldn't then the check be just:
>
> if (zone->per_cpu_pageset)
> return;
>
> Because if it's == &boot_pageset, we are just setting the same values that
> area already there?
>
Right. And zone_pcp_init(), called by zone_init_internals(), becomes a nop for
free_area_init_core_hotplug(). Then I wonder if zone_init_internals() is
needed for hotplug, but that belongs to a later cleanup.
--
Best Regards,
Yan, Zi
next prev parent reply other threads:[~2026-11-03 16:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 2:13 [PATCH v5 0/12] mm: fix allocator races with memory hotplug Gregory Price (Meta)
2026-11-01 2:13 ` [PATCH v5 01/12] mm/page_alloc: reset can_retry_reserves when the slowpath restarts Gregory Price (Meta)
2026-11-01 19:52 ` Zi Yan
2026-11-01 2:13 ` [PATCH v5 02/12] mm/page_alloc: keep the pagesets of an empty zone Gregory Price (Meta)
2026-11-01 20:07 ` Zi Yan
2026-11-03 14:57 ` Vlastimil Babka (SUSE)
2026-11-03 16:04 ` Zi Yan [this message]
2026-11-01 2:13 ` [PATCH v5 03/12] mm, page_alloc: pass zone pointer to trace_reclaim_retry_zone Gregory Price (Meta)
2026-11-01 20:28 ` Zi Yan
2026-11-01 2:13 ` [PATCH v5 04/12] mm/page_alloc: detect zonelist rebuilds from memory hot-add Gregory Price (Meta)
2026-11-01 20:31 ` Zi Yan
2026-11-01 2:13 ` [PATCH v5 05/12] mm/mmzone: read the zoneref slot once in zonelist_zone() Gregory Price (Meta)
2026-11-03 2:54 ` Zi Yan
2026-11-01 2:13 ` [PATCH v5 06/12] mm/page_alloc: snapshot the preferred zone against shrink rebuilds Gregory Price (Meta)
2026-11-03 2:56 ` Zi Yan
2026-11-01 2:13 ` [PATCH v5 07/12] mm/mmzone: read each zoneref slot once when filtering by nodemask Gregory Price (Meta)
2026-11-03 3:01 ` Zi Yan
2026-11-03 15:00 ` Vlastimil Babka (SUSE)
2026-11-01 2:13 ` [PATCH v5 08/12] mm/page_alloc: retry allocations that raced with a zonelist rebuild Gregory Price (Meta)
2026-11-01 2:13 ` [PATCH v5 09/12] mm/hugetlb: retry the pool walk when the zonelist is rebuilt Gregory Price (Meta)
2026-11-01 2:13 ` [PATCH v5 10/12] mm/page_alloc: retry alloc_contig_pages() " Gregory Price (Meta)
2026-11-03 3:13 ` Zi Yan
2026-11-01 2:13 ` [PATCH v5 11/12] mm/mempolicy: read the zoneref slot once in mempolicy_slab_node() Gregory Price (Meta)
2026-11-03 3:14 ` Zi Yan
2026-11-01 2:13 ` [PATCH v5 12/12] mm/mmzone: remove zonelist_node_idx() Gregory Price (Meta)
2026-11-03 3:15 ` Zi Yan
2026-11-01 11:00 ` [PATCH v5 0/12] mm: fix allocator races with memory hotplug Vlastimil Babka (SUSE)
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=DMLPC0D7EWRW.EVYWUONVO18A@nvidia.com \
--to=ziy@nvidia.com \
--cc=Bessel.Wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baoquan.he@linux.dev \
--cc=bigeasy@linutronix.de \
--cc=brendan.jackman@linux.dev \
--cc=clrkwllms@kernel.org \
--cc=david@kernel.org \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=jiang.liu@huawei.com \
--cc=josef@toxicpanda.com \
--cc=joshua.hahnjy@gmail.com \
--cc=justinstitt@google.com \
--cc=kasong@tencent.com \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@techsingularity.net \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=morbo@google.com \
--cc=muchun.song@linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=osalvador@suse.de \
--cc=qi.zheng@linux.dev \
--cc=rakie.kim@sk.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=weixugc@google.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yuanchu@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.