linux-kernel - Re: [GIT PULL] hotfixes for 6.7-rc6

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]

Date: Fri, 15 Dec 2023 12:11:42 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] hotfixes for 6.7-rc6

On Fri, 15 Dec 2023 at 07:16, Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> Yu Zhao (4):
>       mm/mglru: fix underprotected page cache
>       mm/mglru: try to stop at high watermarks
>       mm/mglru: respect min_ttl_ms with memcgs
>       mm/mglru: reclaim offlined memcgs harder

Entirely unrelated to this pull request (which I already pulled and
pushed out, as noted by pr-tracker-bot), since I looked at these it
just reminded me about a question I've had for a while...

Do we have any long-term (or even short-term?) plans to just make
mglru be the one and only model?

Yes, right now it's not just a Kconfig choice, but a real technical
issue too: it depends on having enough flags available, so we have
that "cannot use it on 32-bit with sparsemem".

But I'm hoping there is a plan or a workaround for that?

Because I feel like we really don't want to keep this "two different
models" situation around forever.

                     Linus