From: Ridong <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>, "Michal Koutný" <mkoutny@suse.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"Ridong Chen" <ridong.chen@linux.dev>,
cui.tao@linux.dev, "Ridong Chen" <chenridong@xiaomi.com>
Subject: [PATCH v2 0/2] mm, memcg: fix memory.peak reset clobbering other fds' watermark
Date: Fri, 7 Aug 2026 16:59:58 +0800 [thread overview]
Message-ID: <20260807090000.1532495-1-ridong.chen@linux.dev> (raw)
From: Ridong Chen <chenridong@xiaomi.com>
Two fixes for the per-fd memory.peak / memory.swap.peak handlers added in
c6f53ed8f213. Each open fd reads back max(its own value, the shared
local_watermark), and both bugs live in that scheme.
---
Changes since v1 [1]:
- New patch 1: hold peaks_lock in the peak readers (Sashiko).
- Patch 2: floor the peers with max(usage, local_watermark), mirroring
peak_show(), and skip the writing fd (Johannes Weiner).
[1] https://lore.kernel.org/all/20260730115314.1069089-1-ridong.chen@linux.dev/
Ridong Chen (2):
memcg: acquire peaks_lock when reading memory.peak
mm, memcg: fix memory.peak reset clobbering other fds' watermark
mm/memcontrol.c | 21 ++++++++++++++++-----
1 file changed, 16 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2026-08-07 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 8:59 Ridong [this message]
2026-08-07 8:59 ` [PATCH v2 1/2] memcg: acquire peaks_lock when reading memory.peak Ridong
2026-08-07 9:00 ` [PATCH v2 2/2] mm, memcg: fix memory.peak reset clobbering other fds' watermark Ridong
2026-08-07 20:22 ` [PATCH v2 0/2] " Andrew Morton
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=20260807090000.1532495-1-ridong.chen@linux.dev \
--to=ridong.chen@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@xiaomi.com \
--cc=cui.tao@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox