linux-kernel - Re: Regression, i.MX7 boot failure, Linux v6.1.77

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: <2024021300-traverse-anyplace-7910@gregkh>
Date: Tue, 13 Feb 2024 12:44:48 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Francesco Dolcini <francesco@...cini.it>
Cc: Sasha Levin <sashal@...nel.org>, stable@...r.kernel.org,
	Alexander Stein <alexander.stein@...tq-group.com>,
	Shawn Guo <shawnguo@...nel.org>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, regressions@...ts.linux.dev,
	Max Krummenacher <max.krummenacher@...adex.com>,
	Miquel Raynal <miquel.raynal@...tlin.com>
Subject: Re: Regression, i.MX7 boot failure, Linux v6.1.77

On Tue, Feb 13, 2024 at 12:21:46PM +0100, Francesco Dolcini wrote:
> Hello Sasha,
> kernel v6.1.77 introduces a regression, with a boot failure, on i.MX7,
> with commit db30f469ae8b ("ARM: dts: imx7s: Fix nand-controller #size-cells").
> 
> The issue is known [1][2], changing `#size-cells = <0>` is formally
> correct, but do not play well with the firmware that are deployed on
> those embedded devices, leading to a boot failure.
> 
> A mitigation was implemented in the Linux kernel,
> commit 84549c816dc3 ("mtd: parsers: ofpart: add workaround for #size-cells 0")
> that was merged into v6.3, the firmware was also fixed, however existing
> device using old firmware will not boot anymore if updating to a newer
> kernel.
> 
> I would ask you to drop such a patch from any stable patches queue and
> not backport it to any older kernel.
> 
> To fix v6.1.y I see two options:
>  - backport 84549c816dc3
>  - revert db30f469ae8b
> 
> What do you prefer? Should I send myself a patch?

Backport would be best, that way we are in sync with newer releases.

I'll go queue it up now, thanks.

greg k-h