linux-kernel - Re: [PATCH v3 00/30] Eliminate Dying Memory Cgroup

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0a5af01f-2bb3-4dbe-8d16-f1b56f016dee@lucifer.local>
Date: Thu, 15 Jan 2026 12:40:12 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Qi Zheng <qi.zheng@...ux.dev>, hannes@...xchg.org, hughd@...gle.com,
        mhocko@...e.com, roman.gushchin@...ux.dev, shakeel.butt@...ux.dev,
        muchun.song@...ux.dev, david@...nel.org, ziy@...dia.com,
        harry.yoo@...cle.com, yosry.ahmed@...ux.dev, imran.f.khan@...cle.com,
        kamalesh.babulal@...cle.com, axelrasmussen@...gle.com,
        yuanchu@...gle.com, weixugc@...gle.com, chenridong@...weicloud.com,
        mkoutny@...e.com, hamzamahfooz@...ux.microsoft.com,
        apais@...ux.microsoft.com, lance.yang@...ux.dev, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
        Qi Zheng <zhengqi.arch@...edance.com>
Subject: Re: [PATCH v3 00/30] Eliminate Dying Memory Cgroup

On Wed, Jan 14, 2026 at 09:58:39AM -0800, Andrew Morton wrote:
> On Wed, 14 Jan 2026 19:26:43 +0800 Qi Zheng <qi.zheng@...ux.dev> wrote:
>
> > This patchset is intended to transfer the LRU pages to the object cgroup
> > without holding a reference to the original memory cgroup in order to
> > address the issue of the dying memory cgroup.
>
> Thanks.  I'll add this to mm.git for testing.  A patchset of this
> magnitude at -rc5 is a little ambitious, but Linus is giving us an rc8
> so let's see.
>
> I'll suppress the usual added-to-mm email spray.

Since this is so large and we are late on in the cycle can I in this case
can I explicitly ask for at least 1 sub-M tag on each commit before
queueing for Linus please?

We are seeing kernel bot reports here so let's obviously stabilise this for
a while also.

Thanks, Lorenzo