Re: [PATCH] mm: zswap: honor zero cgroup limits after successful reclaim
From: Yosry Ahmed
Date: Wed Nov 11 2026 - 18:43:17 EST
On Wed, Nov 11, 2026 at 3:23 PM Tomás Senart via B4 Relay
<devnull+ts.perfloop.ai@xxxxxxxxxx> wrote:
>
> From: Tomás Senart <ts@xxxxxxxxxxx>
>
> Commit a65b0e7607cc ("zswap: make shrinking memcg-aware") lets a store
> proceed after a successful cgroup reclaim. That also lets a cgroup
> whose memory.zswap.max was lowered to zero replace an old entry with a
> newly compressed page, although zswap is disabled for that hierarchy.
Why is that a problem? Setting memory.zswap.max to 0 while the cgroup
has active swapping processes is naturally racy. The limit can be set
to 0 right after we check it again anyway?