All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Gregory Price (Meta)" <gourry@gourry.net>, linux-mm@kvack.org
Cc: kernel-team@meta.com, muchun.song@linux.dev, osalvador@suse.de,
	david@kernel.org, akpm@linux-foundation.org, ziy@nvidia.com,
	joshua.hahnjy@gmail.com, rakie.kim@sk.com,
	ying.huang@linux.alibaba.com, ljs@kernel.org, liam@infradead.org,
	vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
	mhocko@suse.com, brendan.jackman@linux.dev, hannes@cmpxchg.org,
	mgorman@techsingularity.net, anshuman.khandual@arm.com
Subject: Re: [PATCH v4 8/8] mm/mempolicy: read the zoneref slot once in mempolicy_slab_node()
Date: Thu, 29 Oct 2026 21:19:40 +0000	[thread overview]
Message-ID: <sashiko-outbox-189948@kernel.org> (raw)
In-Reply-To: <20261028211930.3504634-9-gourry@gourry.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] mm/mempolicy: missing READ_ONCE() on zoneref load in mempolicy_slab_node()
--

commit 4beeef01124c3abac1f730eb599686961d03563c
Author: Gregory Price (Meta) <gourry@gourry.net>

mm/mempolicy: read the zoneref slot once in mempolicy_slab_node()

This commit updates mempolicy_slab_node() to store the zone pointer from
zonelist_zone(z) in a local variable before passing it to zone_to_nid(),
aiming to avoid reading the zoneref slot twice when zonelists are rebuilt in
place during memory offlining.

> diff --git a/mm/mempolicy.c b/mm/mempolicy.c
> index 0884c629670dd..cd63c3e2c029c 100644
> --- a/mm/mempolicy.c
> +++ b/mm/mempolicy.c
> @@ -2176,6 +2176,7 @@ unsigned int mempolicy_slab_node(void)
>  	case MPOL_PREFERRED_MANY:
>  	{
>  		struct zoneref *z;
> +		struct zone *zone;
>  
>  		/*
>  		 * Follow bind policy behavior and start allocation at the
> @@ -2186,7 +2187,8 @@ unsigned int mempolicy_slab_node(void)
>  		zonelist = &NODE_DATA(node)->node_zonelists[ZONELIST_FALLBACK];
>  		z = first_zones_zonelist(zonelist, highest_zoneidx,
>  							&policy->nodes);
> -		return zonelist_zone(z) ? zonelist_node_idx(z) : node;
> +		zone = zonelist_zone(z);
> +		return zone ? zone_to_nid(zone) : node;

[Severity: Medium]
Does storing the result of zonelist_zone(z) in a local variable guarantee a
single load of z->zone without READ_ONCE()?

In include/linux/mmzone.h, both zonelist_zone() and zone_to_nid() are static
inline helpers performing plain C loads:

static inline struct zone *zonelist_zone(struct zoneref *zoneref)
{
	return zoneref->zone;
}

When a task with an MPOL_BIND or MPOL_PREFERRED_MANY mempolicy calls
kmem_cache_alloc_noprof() -> mempolicy_slab_node() concurrently with
offline_pages() -> build_all_zonelists() rewriting the zonelist in place,
inlining zonelist_zone() and zone_to_nid() lowers this to a plain load of
z->zone. Without READ_ONCE(), this remains an unmarked data race, and the
compiler is still permitted to reload z->zone from memory and pass NULL to
zone_to_nid().

Earlier commits in this series ("mm/page_alloc: snapshot the preferred zone
against shrink rebuilds" and "mm/mmzone: read each zoneref slot once when
filtering by nodemask") used READ_ONCE(ac->preferred_zoneref->zone) and
READ_ONCE(z->zone) to enforce a single load. Should mempolicy_slab_node()
(or zonelist_zone() itself) use READ_ONCE(z->zone) here as well?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261028211930.3504634-1-gourry@gourry.net?part=8


  parent reply	other threads:[~2026-10-29 21:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 21:19 [PATCH v4 0/8] mm: fix allocator races with memory hotplug Gregory Price (Meta)
2026-10-28 21:19 ` [PATCH v4 1/8] mm/page_alloc: reset can_retry_reserves when the slowpath restarts Gregory Price (Meta)
2026-10-29 13:37   ` Vlastimil Babka (SUSE)
2026-10-29 16:31     ` Gregory Price (Meta)
2026-10-28 21:19 ` [PATCH v4 2/8] mm/page_alloc: detect zonelist rebuilds from memory hot-add Gregory Price (Meta)
2026-10-28 21:19 ` [PATCH v4 3/8] mm/page_alloc: snapshot the preferred zone against shrink rebuilds Gregory Price (Meta)
2026-10-29 15:21   ` Vlastimil Babka (SUSE)
2026-10-28 21:19 ` [PATCH v4 4/8] mm/mmzone: read each zoneref slot once when filtering by nodemask Gregory Price (Meta)
2026-10-29 15:51   ` Vlastimil Babka (SUSE)
2026-10-28 21:19 ` [PATCH v4 5/8] mm/page_alloc: retry allocations that raced with a zonelist rebuild Gregory Price (Meta)
2026-10-29 17:47   ` Vlastimil Babka (SUSE)
2026-10-28 21:19 ` [PATCH v4 6/8] mm/hugetlb: retry the pool walk when the zonelist is rebuilt Gregory Price (Meta)
2026-10-29 18:08   ` Vlastimil Babka (SUSE)
2026-10-30  1:37     ` Gregory Price (Meta)
2026-10-28 21:19 ` [PATCH v4 7/8] mm/page_alloc: retry alloc_contig_pages() " Gregory Price (Meta)
2026-10-29 18:10   ` Vlastimil Babka (SUSE)
2026-10-28 21:19 ` [PATCH v4 8/8] mm/mempolicy: read the zoneref slot once in mempolicy_slab_node() Gregory Price (Meta)
2026-10-29 18:16   ` Vlastimil Babka (SUSE)
2026-10-29 21:19   ` sashiko-bot [this message]
2026-10-29 18:52 ` [PATCH v4 0/8] mm: fix allocator races with memory hotplug Gregory Price (Meta)

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=sashiko-outbox-189948@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=brendan.jackman@linux.dev \
    --cc=david@kernel.org \
    --cc=gourry@gourry.net \
    --cc=hannes@cmpxchg.org \
    --cc=joshua.hahnjy@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=liam@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=rakie.kim@sk.com \
    --cc=rppt@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=ying.huang@linux.alibaba.com \
    --cc=ziy@nvidia.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.