Re: [PATCH] mm: zswap: honor zero cgroup limits after successful reclaim

[Tomás Senart]

On Thu, Nov 12, 2026 at 12:28 AM Yosry Ahmed <yosry@xxxxxxxxxx> wrote:
> 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?

Agreed on the race, this doesn't try to fix it.

The case here is different: with the limit already at 0, every store
writes back an old entry and then stores the new page anyway, until
the pool drains. It's bounded, so if it's not worth a special case,
happy to drop it.

Tomás