From: Ridong Chen <ridong.chen@linux.dev>
To: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "Muchun Song" <muchun.song@linux.dev>,
"Tejun Heo" <tj@kernel.org>, "David Finkel" <davidf@vimeo.com>,
"Michal Koutný" <mkoutny@suse.com>,
cgroups@vger.kernel.org (open list:CONTROL GROUP - MEMORY
RESOURCE CONTROLLER (MEMCG)),
linux-mm@kvack.org (open list:CONTROL GROUP - MEMORY RESOURCE
CONTROLLER (MEMCG)),
linux-kernel@vger.kernel.org, "Tao Cui" <cuitao@kylinos.cn>,
"Ridong Chen" <ridong.chen@linux.dev>,
"Ridong Chen" <chenridong@xiaomi.com>
Subject: [PATCH v3 1/2] memcg: acquire peaks_lock when reading memory.peak
Date: Fri, 14 Aug 2026 09:29:23 +0800 [thread overview]
Message-ID: <20260814012924.2388613-2-ridong.chen@linux.dev> (raw)
In-Reply-To: <20260814012924.2388613-1-ridong.chen@linux.dev>
From: Ridong Chen <chenridong@xiaomi.com>
Sashiko reported that a reader can transiently observe a lower peak
within a race window [1]. peak_show() returns
max(local_watermark, ofp->value), but peak_write() updates those two
under peaks_lock while the reader takes no lock. The interleaving is:
writer (reset on fd A) reader (fd B)
---------------------- -------------
usage = page_counter_read(pc)
WRITE_ONCE(local_watermark, usage)
// watermark lowered to usage
lw = READ_ONCE(local_watermark)
// sees the lowered usage
val = READ_ONCE(ofp->value)
// B's value not updated yet
return max(lw, val)
// both low -> low peak
WRITE_ONCE(peer_ctx->value, usage)
// B updated, but too late
Fix it by acquiring peaks_lock when reading the peak, so the reader sees
a consistent snapshot of local_watermark and the per-fd values. The same
race applies to memory.swap.peak, which shares peaks_lock and the
peak_write() path, so take the lock there as well.
[1] https://sashiko.dev/#/patchset/20260730115314.1069089-1-ridong.chen@linux.dev?part=1
Fixes: c6f53ed8f213 ("mm, memcg: cg2 memory{.swap,}.peak write handlers")
Assisted-by: Claude:claude-opus-4-8
Signed-off-by: Ridong Chen <chenridong@xiaomi.com>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
---
mm/memcontrol.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 17da1f43b7d3..6dd8756870ff 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -4713,8 +4713,13 @@ static int peak_show(struct seq_file *sf, void *v, struct page_counter *pc)
static int memory_peak_show(struct seq_file *sf, void *v)
{
struct mem_cgroup *memcg = mem_cgroup_from_css(seq_css(sf));
+ int ret;
- return peak_show(sf, v, &memcg->memory);
+ spin_lock(&memcg->peaks_lock);
+ ret = peak_show(sf, v, &memcg->memory);
+ spin_unlock(&memcg->peaks_lock);
+
+ return ret;
}
static int peak_open(struct kernfs_open_file *of)
@@ -5858,8 +5863,13 @@ static u64 swap_current_read(struct cgroup_subsys_state *css,
static int swap_peak_show(struct seq_file *sf, void *v)
{
struct mem_cgroup *memcg = mem_cgroup_from_css(seq_css(sf));
+ int ret;
- return peak_show(sf, v, &memcg->swap);
+ spin_lock(&memcg->peaks_lock);
+ ret = peak_show(sf, v, &memcg->swap);
+ spin_unlock(&memcg->peaks_lock);
+
+ return ret;
}
static ssize_t swap_peak_write(struct kernfs_open_file *of, char *buf,
--
2.34.1
next prev parent reply other threads:[~2026-08-14 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 1:29 [PATCH v3 0/2] mm, memcg: fix memory.peak reset clobbering other fds' watermark Ridong Chen
2026-08-14 1:29 ` Ridong Chen [this message]
2026-08-14 2:12 ` [PATCH v3 1/2] memcg: acquire peaks_lock when reading memory.peak Muchun Song
2026-08-14 2:25 ` Ridong Chen
2026-08-14 1:29 ` [PATCH v3 2/2] mm, memcg: fix memory.peak reset clobbering other fds' watermark Ridong Chen
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=20260814012924.2388613-2-ridong.chen@linux.dev \
--to=ridong.chen@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@xiaomi.com \
--cc=cuitao@kylinos.cn \
--cc=davidf@vimeo.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=tj@kernel.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 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.