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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAODwPW8AJuWq5_5Ktb4bo=_2jUgzrUvntdmqh8Pb+bFbq+Txsg@mail.gmail.com>
Date:   Wed, 8 Nov 2023 15:53:52 -0800
From:   Julius Werner <jwerner@...omium.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>,
        Tzung-Bi Shih <tzungbi@...nel.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

Yeah, if the kernel wanted to make use of coreboot display init on
those boards, it would have to reserve its own framebuffer space and
need to have at least enough of a driver for the display controller to
be able to tell it which address it picked. Until someone implements
that, erroring out for those cases makes sense.

Reviewed-by: Julius Werner <jwerner@...omium.org>