From: Hans de Goede <hdegoede@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
linux-efi <linux-efi@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] efi/bgrt: Accept BGRT tables with a version of 0 on Lenovo laptops
Date: Fri, 31 Jan 2020 13:47:40 +0100 [thread overview]
Message-ID: <1e7dc0f5-6903-0382-cf32-54b1b095930f@redhat.com> (raw)
In-Reply-To: <CAKv+Gu_dE+pi7CSANOXEP2xenRirWQg5H71t5f4eah8-XZpbxQ@mail.gmail.com>
Hi,
On 1/28/20 8:48 AM, Ard Biesheuvel wrote:
> On Sun, 26 Jan 2020 at 16:02, Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> Some (somewhat older) Lenovo laptops have a correct BGRT table, except
>> that the version field is 0 instead of 1.
>>
>> Quickly after finding this out, even before submitting a first version of
>> this patch upstream, the list of DMI matches for affected models grew to
>> 3 models (all Ivy Bridge based).
>>
>> So rather then maintaining an ever growing list with DMI matches for
>> affected Lenovo models, this commit simply checks if the vendor is Lenovo
>> when the version is 0 and in that case accepts the out of spec version
>> working around the Lenovo firmware bug.
>>
>> Cc: stable@vger.kernel.org
>> BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1791273
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> drivers/firmware/efi/efi-bgrt.c | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/firmware/efi/efi-bgrt.c b/drivers/firmware/efi/efi-bgrt.c
>> index b07c17643210..3a2d6d3a590b 100644
>> --- a/drivers/firmware/efi/efi-bgrt.c
>> +++ b/drivers/firmware/efi/efi-bgrt.c
>> @@ -15,6 +15,7 @@
>> #include <linux/acpi.h>
>> #include <linux/efi.h>
>> #include <linux/efi-bgrt.h>
>> +#include <linux/dmi.h>
>>
>> struct acpi_table_bgrt bgrt_tab;
>> size_t bgrt_image_size;
>> @@ -42,7 +43,12 @@ void __init efi_bgrt_init(struct acpi_table_header *table)
>> return;
>> }
>> *bgrt = *(struct acpi_table_bgrt *)table;
>> - if (bgrt->version != 1) {
>> + /*
>> + * Some older Lenovo laptops have a correct BGRT table, except that
>> + * the version field is 0 instead of 1.
>> + */
>> + if (bgrt->version != 1 &&
>> + !(bgrt->version == 0 && dmi_name_in_vendors("LENOVO"))) {
>> pr_notice("Ignoring BGRT: invalid version %u (expected 1)\n",
>> bgrt->version);
>> goto out;
>
> Hi Hans,
>
> Given that the ACPI spec only defines a single version for this table,
> which is version #1, wouldn't it be simpler to just assume that
> version #0 means version #1 in all cases, rather than using DMI
> matches for that? There is no risk of misidentifying another table
> version, since none exist ...
Ok, I will prepare a new version doing this.
Regards,
Hans
prev parent reply other threads:[~2020-01-31 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 15:02 [PATCH] efi/bgrt: Accept BGRT tables with a version of 0 on Lenovo laptops Hans de Goede
2020-01-28 7:48 ` Ard Biesheuvel
2020-01-31 12:47 ` Hans de Goede [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1e7dc0f5-6903-0382-cf32-54b1b095930f@redhat.com \
--to=hdegoede@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ardb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).