linux-kernel - Re: [GIT PULL] Devicetree updates for v6.13

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: <CAGXv+5FLkZbZVHNkfRWuT+OioZ0TG=u2WfaFCx-jZFi73QHnVg@mail.gmail.com>
Date: Mon, 25 Nov 2024 18:34:51 +0800
From: Chen-Yu Tsai <wenst@...omium.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: Sasha Levin <sashal@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 
	Rob Herring <robh@...nel.org>, Linus Torvalds <torvalds@...ux-foundation.org>, 
	Saravana Kannan <saravanak@...gle.com>, 
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>, 
	linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, 
	Matthias Brugger <matthias.bgg@...il.com>
Subject: Re: [GIT PULL] Devicetree updates for v6.13

On Mon, Nov 25, 2024 at 5:48 PM AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com> wrote:
>
> Il 24/11/24 17:59, Sasha Levin ha scritto:
> > On Sun, Nov 24, 2024 at 05:47:33PM +0100, Krzysztof Kozlowski wrote:
> >> On 24/11/2024 17:29, Sasha Levin wrote:
> >>> Hi Rob,
> >>>
> >>> On Mon, Nov 18, 2024 at 03:07:30PM -0600, Rob Herring wrote:
> >>>>      of: WARN on deprecated #address-cells/#size-cells handling
> >>>
> >>> With the commit above, I've started seeing boot warnings on a few
> >>
> >> And same boards do not report problems on the next?
> >
> > Looks like they do. I haven't checked it previously, but I see that we
> > have similar warnings on a few boards that KernelCI is testing -next on.
> >
>
> That's... horrendous.
>
> I hope that we can get a proper fix with a bootloader update on these (now very
> old) devices... Adding a Google engineer to the loop so that he can follow up
> internally.

AFAIK that's unlikely going to happen given the resources needed from
the ODMs for a firmware re-qualification. Or we would have fixed the GIC
bug in ATF and had pseudo-NMI.

Some of the firmware code involved is 10 years old, so even the RK3399
Chromebooks, which no longer have support, could suffer from this as
well.

> The alternative would be to hack-in a firmware node to mt8183-kukui.dtsi, but....
> ...ugh. That'd be indeed a hack for the sole purpose of fixing a bootloader that
> is acting in a broken way, and I don't like that at all (...and I'm sure I'm not
> alone!).


Regards
ChenYu