linux-kernel - Re: [PATCH] arm64: dts: mediatek: Apply all DT overlays at build time

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: <CAL_JsqK4jvZQTQAXCjPgxBCUiENGKgkgaDgZ680QqL1XpS6bbw@mail.gmail.com>
Date: Tue, 18 Nov 2025 06:31:08 -0600
From: Rob Herring <robh@...nel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Cc: Matthias Brugger <matthias.bgg@...il.com>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, linux-kernel@...r.kernel.org, 
	linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org, 
	devicetree@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: mediatek: Apply all DT overlays at build time

On Tue, Nov 18, 2025 at 3:36 AM AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com> wrote:
>
> Il 17/11/25 22:13, Rob Herring (Arm) ha scritto:
> > It's a requirement that DT overlays be applied at build time in order to
> > validate them as overlays are not validated on their own.
> >
> > Add targets for all the Mediatek overlays.
> >
> > Signed-off-by: Rob Herring (Arm) <robh@...nel.org>
> > ---
> > This will soon be a warning[1].
> >
> > Note that if it is desired that the combined .dtb is not installed, then
> > the combined .dtb should be added to 'dtb-' variable instead.
> >
>
> Uhm, sorry, can't we do something such that we don't generate a DTB with a
> preapplied overlay?
>
> Even something like generating those and deleting before build finalization
> could work, I guess, though that'd be hacky maybe.
>
> I don't know if this is the case, but I'm worried that various people have
> scripts to copy DTBs somewhere (in some partition) or embed those in images,
> and if they get the preapplied overlay dtbs in the same place, havoc could
> happen as the bootloaders might be selecting wrong dtbs (as a plus, there is
> no dtbo that varies machine compatible strings, rightfully).

If they aren't using dtbs_install for that, then that is their
problem. When we moved all the arm32 DTs to vendor directories,
dtbs_install maintained the old structure which seemed sufficient to
not break folks. The same should apply here.

Rob