linux-kernel - A path forward to cleaning up dying cgroups?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z6OkXXYDorPrBvEQ@hm-sls2>
Date: Wed, 5 Feb 2025 12:48:13 -0500
From: Hamza Mahfooz <hamzamahfooz@...ux.microsoft.com>
To: linux-mm@...ck.org
Cc: Roman Gushchin <roman.gushchin@...ux.dev>,
	Johannes Weiner <hannes@...xchg.org>,
	Shakeel Butt <shakeelb@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>, cgroups@...r.kernel.org,
	linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>,
	Michal Koutný <mkoutny@...e.com>,
	Michal Hocko <mhocko@...nel.org>,
	Muchun Song <muchun.song@...ux.dev>,
	Allen Pais <apais@...ux.microsoft.com>,
	Hamza Mahfooz <hamzamahfooz@...ux.microsoft.com>,
	Yosry Ahmed <yosryahmed@...gle.com>
Subject: A path forward to cleaning up dying cgroups?

I was just curious as to what the status of the issue described in [1]
is. It appears that the last time someone took a stab at it was in [2].

Though it seems like there has been relative silence regarding it since
then. So, has there been any discussion regarding the issue since then
and does anyone know if there is consensus on how we should go about
resolving this issue within the kernel?

BR,
Hamza

[1] https://lwn.net/Articles/895431/
[2] https://lore.kernel.org/r/20220621125658.64935-1-songmuchun@bytedance.com/