linux-kernel - Re: [RFC PATCH v2 1/2] ARM/mm/fault: always goto bad_area when handling with page faults of kernel address

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: <20251128172242.cCNBVf7H@linutronix.de>
Date: Fri, 28 Nov 2025 18:22:42 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Xie Yuanbin <xieyuanbin1@...wei.com>, akpm@...ux-foundation.org,
	arnd@...db.de, brauner@...nel.org, david.laight@...box.com,
	hch@....de, jack@...e.com, kuninori.morimoto.gx@...esas.com,
	liaohua4@...wei.com, lilinjie8@...wei.com,
	linux-arm-kernel@...ts.infradead.org, linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	lorenzo.stoakes@...cle.com, marc.zyngier@....com, nico@...xnic.net,
	pangliyuan1@...wei.com, pfalcato@...e.de, punitagrawal@...il.com,
	rjw@...ysocki.net, rppt@...nel.org, tony@...mide.com,
	vbabka@...e.cz, viro@...iv.linux.org.uk, wangkefeng.wang@...wei.com,
	will@...nel.org, wozizhi@...weicloud.com
Subject: Re: [RFC PATCH v2 1/2] ARM/mm/fault: always goto bad_area when
 handling with page faults of kernel address

On 2025-11-28 17:01:18 [+0000], Russell King (Oracle) wrote:
> > I hope Russell will add them once he gets to it. They got reviewed, I
> > added them to the patch system.
> 
> I'm not sure which patches you're talking about, but discussion is
> still ongoing, so it would be greatly premature to merge anything.

This thread
	https://lore.kernel.org/all/20251110145555.2555055-1-bigeasy@linutronix.de/

and the patches are 9459/1 to 9463/1 in your patch system. They address
other issues, not this one.

> https://lore.kernel.org/r/aSmUnZZATTn3JD7m@willie-the-truck
> 
> There are now many threads each with their own discussion, which
> makes it more difficult to work out which is the implementation that
> should be merged. Clearly, not everyone knows about the other
> discussion threads.

So Will suggested to let change the handler and handle this case. The
other patch is avoiding handling addr > TASK_SIZE.
Any preferences from your side?

Sebastian