From: Muchun Song <muchun.song@linux.dev>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Chris Down <chris@chrisdown.name>,
Meta kernel team <kernel-team@meta.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH] mm/page_counter: use WRITE_ONCE() for emin/elow when parent is the root
Date: Thu, 22 Oct 2026 10:18:17 +0800 [thread overview]
Message-ID: <DE0BFDD2-1BE5-4FB1-AE66-1D4C7DFACA1F@linux.dev> (raw)
In-Reply-To: <20261021204818.3431099-1-shakeel.butt@linux.dev>
> On Oct 22, 2026, at 04:48, Shakeel Butt <shakeel.butt@linux.dev> wrote:
>
> page_counter_calculate_protection() runs without locks. Several
> reclaimers can update the same counter's emin and elow at the same
> time, and readers such as mem_cgroup_below_min(), mem_cgroup_protection()
> and the dmem eviction code load them with READ_ONCE().
>
> Commit b3a7822e5e75 ("mm, memcg: prevent mem_cgroup_protected store
> tearing") made the main path store emin and elow with WRITE_ONCE(), but
> it missed the early return for a counter whose parent is the reclaim
> root. Those two stores are the only plain accesses to emin and elow
> left.
>
> With CONFIG_KCSAN_STRICT=y, a few tasks writing to the same cgroup's
> memory.reclaim trigger reports like this within seconds:
>
> BUG: KCSAN: data-race in page_counter_calculate_protection / shrink_node
>
> read (marked) to 0xff1f91b146d40e40 of 8 bytes by task 163 on cpu 4:
> shrink_node+0x57a/0x1210
> do_try_to_free_pages+0x194/0x930
> try_to_free_mem_cgroup_pages+0x204/0x3f0
> user_proactive_reclaim+0x28a/0x4d0
> memory_reclaim+0x35/0x50
> ...
>
> write to 0xff1f91b146d40e40 of 8 bytes by task 167 on cpu 6:
> page_counter_calculate_protection+0x1fa/0x360
> mem_cgroup_calculate_protection+0x4e/0x70
> shrink_node+0x53e/0x1210
> ...
>
> The default KCSAN config does not report it, because it treats aligned
> word-sized plain writes as atomic.
>
> Use WRITE_ONCE() for these two stores as well.
>
> There is no functional change. Readers already accept stale values, and
> compilers emit a single word-sized store either way: with GCC 14 the
> x86-64 object code is the same before and after this change.
>
> Fixes: b3a7822e5e75 ("mm, memcg: prevent mem_cgroup_protected store tearing")
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Signed-off-by: Shakeel Butt <shakeel.butt@linux.dev>
Acked-by: Muchun Song <muchun.song@linux.dev>
Thanks.
prev parent reply other threads:[~2026-10-22 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 20:48 Shakeel Butt
2026-10-21 21:24 ` Gregory Price
2026-10-22 0:53 ` SJ Park
2026-10-22 2:18 ` Muchun Song [this message]
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=DE0BFDD2-1BE5-4FB1-AE66-1D4C7DFACA1F@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=sashiko-bot@kernel.org \
--cc=shakeel.butt@linux.dev \
/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
all inboxes | Powered by JetHome®