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: <CACRpkdY9VS1H642wSUsLvwi91YOwXGkiePdq+JktDSeiWTon8w@mail.gmail.com>
Date: Fri, 12 Sep 2025 14:46:31 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Richard Weinberger <richard@....at>, Dave Hansen <dave@...1.net>, ksummit <ksummit@...ts.linux.dev>, 
	linux-kernel <linux-kernel@...r.kernel.org>, 
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>, 
	linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>, linux-mips <linux-mips@...r.kernel.org>, 
	linux-mm <linux-mm@...ck.org>, imx <imx@...ts.linux.dev>, 
	Christophe Leroy <christophe.leroy@...roup.eu>, 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>, Matthew Wilcox <willy@...radead.org>, 
	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 Fri, Sep 12, 2025 at 12:31 PM Arnd Bergmann <arnd@...db.de> wrote:
> On Wed, Sep 10, 2025, at 22:33, Richard Weinberger wrote:
> > ----- Ursprüngliche Mail -----
> >> Von: "Dave Hansen" <dave@...1.net>
> >>> Even with a new memory split, which could utilize most of the
> >>> available memory, I expect there to be issues with various
> >>> applications and FPGA device drivers.
>
> I also remember driver problems on older Marvell NAS systems, which
> we never fully figured out, my best guess in retrospect is that these
> had devices with DMA address restrictions, and if lowmem is small
> enough it would always work, but any lowmem allocation above the
> hardware DMA address limit would cause data corruption.

This kind of mess is often also driver problems, in the Kirkwood MMC
driver there is some dated code traversing sglists iteratively
instead of using sg_miter() on !DMA which I think is not entirely
safe either.

I wanted to fix that driver but the hardware is in my NAS and
all the time someone is watching a movie from it :D

Yours,
Linus Walleij