linux-kernel - Re: [TECH TOPIC] Reaching consensus on CONFIG

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: <CACRpkdZZZNV5BdNhyXEK__=EJLjDtAEsc2Kv4Tv53+=Mv-8R=w@mail.gmail.com>
Date: Wed, 10 Sep 2025 11:49:55 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Matthew Wilcox <willy@...radead.org>, Russell King <rmk+kernel@...linux.org.uk>
Cc: Arnd Bergmann <arnd@...db.de>, ksummit@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linuxppc-dev@...ts.ozlabs.org, 
	linux-mips@...r.kernel.org, linux-mm@...ck.org, imx@...ts.linux.dev, 
	Christophe Leroy <christophe.leroy@...roup.eu>, Richard Weinberger <richard@....at>, 
	Lucas Stach <l.stach@...gutronix.de>, Geert Uytterhoeven <geert+renesas@...der.be>, 
	Ankur Arora <ankur.a.arora@...cle.com>, David Hildenbrand <david@...hat.com>, 
	Mike Rapoport <rppt@...nel.org>, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, 
	Andrew Morton <akpm@...ux-foundation.org>, "Liam R. Howlett" <Liam.Howlett@...cle.com>, 
	Vlastimil Babka <vbabka@...e.cz>, Suren Baghdasaryan <surenb@...gle.com>, Ira Weiny <ira.weiny@...el.com>, 
	Nishanth Menon <nm@...com>, Heiko Stübner <heiko@...ech.de>, 
	Alexander Sverdlin <alexander.sverdlin@...il.com>, 
	"Chester A. Unal" <chester.a.unal@...nc9.com>, 
	Sergio Paracuellos <sergio.paracuellos@...il.com>, Andreas Larsson <andreas@...sler.com>
Subject: Re: [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout

On Wed, Sep 10, 2025 at 3:46 AM Matthew Wilcox <willy@...radead.org> wrote:

> I don't mind that the feature remains ... unless it causes us trouble.
> Which it currently does.  Perhaps we could start by removing HIGHPTE?
> There was a certain amount of complexity introduced into the page fault
> path when support for that was introduced.  x86 removed support for it,
> so it's just ARM left before we can remove the complexity again.

I sent an RFC patch so we can see what Russell has to say about this,
it is currently only enabled by default on the VT8500 machine.

Yours,
Linus Walleij