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]
Date:   Fri, 21 Apr 2023 09:42:25 -0400
From:   "Pierre Asselin" <pa@...ix.com>
To:     "Thomas Zimmermann" <tzimmermann@...e.de>
Cc:     "Linux regressions mailing list" <regressions@...ts.linux.dev>,
        "Pierre Asselin" <pa@...ix.com>, dri-devel@...ts.freedesktop.org,
        "Daniel Vetter" <daniel.vetter@...ll.ch>,
        "Javier Martinez Canillas" <javierm@...hat.com>,
        linux-kernel@...r.kernel.org,
        "Hans de Goede" <hdegoede@...hat.com>,
        "Ard Biesheuvel" <ardb@...nel.org>
Subject: Re: [PATCH v3] firmware/sysfb: Fix VESA format selection

Thomas Zimmerman writes:
>
> Am 21.04.23 um 13:32 schrieb Linux regression tracking (Thorsten
> Leemhuis):
>>
>> Pierre, Tomas, Javier, et. al: how many "legacy BIOSes" do we suspect
>> are affected by this?

So far, two:
1) my Gateway laptop (Intel(R) Core(TM) Duo CPU,
   Phoenix BIOS 83.08 Revision: 131.8 Release Date: 03/06/07)
2) my Dell Precision T3610 (Intel(R) Xeon(R) CPU E5-1650,
   Dell BIOS A19 Revision: 65.19 Release Date: 09/11/2019)

I don't know how to give a more precise description.

>> might it be worth asking Linus to merge this patch directly[1]?
>
> IMHO it's a fairly obscure bug and certainly not a release blocker. I'll
> send it through the regular channels of the DRM subsystem.

I agree.  Even when the regression bites, it's not a blocker.  The screen
is strange but readable.

--PA

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ