Re: [PATCH v2 0/2] mm, memcg: fix memory.peak reset clobbering other fds' watermark
From: Andrew Morton
Date: Fri Aug 07 2026 - 16:23:09 EST
On Fri, 7 Aug 2026 16:59:58 +0800 Ridong <ridong.chen@xxxxxxxxx> wrote:
> 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.
Thanks.
We're missing the preferred description of the worst-case
userspace-visible effects of the bug. It appears they're quite minor
so I'll assume this series is a post-7.2 thing.
Sashiko might have found a similar race on the writer side:
https://sashiko.dev/#/patchset/20260807090000.1532495-1-ridong.chen@xxxxxxxxx