linux-kernel - Re: [PATCH v1 1/1] serial: core: Restore sysfs fwnode information

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

Message-ID: <713aa37f-161d-4f08-9417-d7d2abdcdfd9@sirena.org.uk>
Date: Thu, 18 Dec 2025 16:54:42 +0000
From: Mark Brown <broonie@...nel.org>
To: Marek Szyprowski <m.szyprowski@...sung.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jiri Slaby <jirislaby@...nel.org>
Subject: Re: [PATCH v1 1/1] serial: core: Restore sysfs fwnode information

On Thu, Dec 18, 2025 at 04:29:55PM +0100, Marek Szyprowski wrote:
> On 27.11.2025 17:36, Andy Shevchenko wrote:
> > The change that restores sysfs fwnode information does it only for OF cases.
> > Update the fix to cover all possible types of fwnodes.

> This patch landed in today's linux-next as commit 24ec03cc5512 ("serial: 
> core: Restore sysfs fwnode information"). In my tests I found that it 
> breaks booting of most of my test boards (ARM 32 and 64 bit). 
> Unfortunately I cannot provide anything useful besides the information 
> that booting stops and system doesn't reach shell. There is nothing 
> suspicious in the kernel logs. I suspect a memory trashing. Reverting 
> $subject on top of linux-next fixes booting.

I'm also seeing this in my lab and Arm's lab, there are a few systems
that survive but it's a small minority.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)