linux-kernel - Re: [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols

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: <87jzg4y57g.fsf@miraculix.mork.no>
Date: Sun, 25 Aug 2024 17:47:47 +0200
From: Bjørn Mork <bjorn@...k.no>
To: "Maciej W. Rozycki" <macro@...am.me.uk>
Cc: Jiaxun Yang <jiaxun.yang@...goat.com>,
        Thomas Bogendoerfer <tsbogend@...ha.franken.de>,
        "linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
        linux-kernel@...r.kernel.org,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH] MIPS: fw: Gracefully handle unknown firmware protocols

"Maciej W. Rozycki" <macro@...am.me.uk> writes:
> On Sun, 25 Aug 2024, Bjørn Mork wrote:
>
>> But I can't make that match what U-Boot does.  AFAICS,
>> u-boot/arch/mips/lib/bootm.c doesn't care about 32 or 64 bit, and simply
>> does:
>
>  U-Boot isn't the only firmware used with MIPS systems, and in fact it's 
> quite a recent addition; e.g. DEC REX and SGI ARCS firmware goes back at 
> least to 1990 and we continue supporting these systems.  There's also CFE, 
> PMON, YAMON, etc.

I know.  That's what I'm trying to make us support :-)

We can't blindly assume that all those firmwares implement the exact
same command line and environment protocol as U-Boot.  Yamon obviously
uses something similar enough.  But what about the others?

As mentioned, we're currently failing to boot from Bootware because of
the relaxed checking here.  Something needs to be done about that.


Bjørn