linux-kernel - Re: [PATCH 5.10 23/49] ACPI: video: Add DMI quirk for GIGABYTE GB-BXBT-2807

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: <YEoO82QF7Y8kTif0@kroah.com>
Date:   Thu, 11 Mar 2021 13:37:07 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Pavel Machek <pavel@...x.de>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        "Jasper St. Pierre" <jstpierre@...heye.net>,
        Chris Chiu <chiu@...lessos.org>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 5.10 23/49] ACPI: video: Add DMI quirk for GIGABYTE
 GB-BXBT-2807

On Wed, Mar 10, 2021 at 09:04:58PM +0100, Pavel Machek wrote:
> Hi!
> 
> On Wed 2021-03-10 14:23:34, gregkh@...uxfoundation.org wrote:
> > From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> > 
> > From: Jasper St. Pierre <jstpierre@...heye.net>
> 
> Something is funny with the From header here. But that's not main
> thing -- this patch is evil.

That is odd...

> 
> > 
> > [ Upstream commit 25417185e9b5ff90746d50769d2a3fcd1629e254 ]
> > 
> > The GIGABYTE GB-BXBT-2807 is a mini-PC which uses off the shelf
> > components, like an Intel GPU which is meant for mobile systems.
> > As such, it, by default, has a backlight controller exposed.
> > 
> > Unfortunately, the backlight controller only confuses userspace, which
> > sees the existence of a backlight device node and has the unrealistic
> > belief that there is actually a backlight there!
> > 
> > Add a DMI quirk to force the backlight off on this system.
> 
> > +++ b/drivers/acpi/video_detect.c
> > @@ -140,6 +140,13 @@ static const struct dmi_system_id video_detect_dmi_table[] = {
> >  	},
> >  	{
> >  	.callback = video_detect_force_vendor,
> > +	.ident = "GIGABYTE GB-BXBT-2807",
> > +	.matches = {
> > +		DMI_MATCH(DMI_SYS_VENDOR, "GIGABYTE"),
> > +		DMI_MATCH(DMI_PRODUCT_NAME, "GB-BXBT-2807"),
> > +		},
> > +	},
> > +	{
> >  	.ident = "Sony VPCEH3U1E",
> >  	.matches = {
> >  		DMI_MATCH(DMI_SYS_VENDOR, "Sony Corporation"),
> 
> Yup, and it looks like this fixes the problem for GIGABYTE
> GB-BXBT-2807 but re-introduces the problem for Sony VPCEH3U1E, because
> its .callback is now NULL.

That's what upstream has right now, for 5.11, so I'll take this for now
and if upstream changes it, I'll take that patch as well.

thanks,

greg k-h