linux-kernel - Re: [PATCH] firmware: coreboot: framebuffer: Avoid invalid zero physical address

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: <ZYzourLcnrxRubaG@google.com>
Date: Thu, 28 Dec 2023 11:17:14 +0800
From: Tzung-Bi Shih <tzungbi@...nel.org>
To: Alper Nebi Yasak <alpernebiyasak@...il.com>
Cc: linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	chrome-platform@...ts.linux.dev,
	Patrick Georgi <pgeorgi@...omium.org>,
	Julius Werner <jwerner@...omium.org>,
	Samuel Holland <samuel@...lland.org>, coreboot@...eboot.org,
	Brian Norris <briannorris@...omium.org>
Subject: Re: [PATCH] firmware: coreboot: framebuffer: Avoid invalid zero
 physical address

On Wed, Nov 08, 2023 at 09:25:13PM +0300, Alper Nebi Yasak wrote:
> On ARM64 systems coreboot defers framebuffer allocation to its payload,
> to be done by a libpayload function call. In this case, coreboot tables
> still include a framebuffer entry with display format details, but the
> physical address field is set to zero (as in [1], for example).
> 
> Unfortunately, this field is not automatically updated when the
> framebuffer is initialized through libpayload, citing that doing so
> would invalidate checksums over the entire coreboot table [2].
> 
> [...]

Applied, thanks!

[1/1] firmware: coreboot: framebuffer: Avoid invalid zero physical address
        commit: ecea08916418a94f99f89c543303877cb6e08a11

Just realized the bot didn't send the mail for the patch.