linux-kernel - RE: keyboard backlight max_brightness bug on Dell Latitude E6410

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: <85b11afa464948a1abcede55b7f66a25@ausx13mpc120.AMER.DELL.COM>
Date:   Mon, 2 Oct 2017 13:06:46 +0000
From:   <Mario.Limonciello@...l.com>
To:     <pali.rohar@...il.com>, <andy.shevchenko@...il.com>
CC:     <gabriel@...gnowsys.com>, <gabriele.mzt@...il.com>,
        <dvhart@...radead.org>, <andy@...radead.org>,
        <platform-driver-x86@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: RE: keyboard backlight max_brightness bug on Dell Latitude E6410

> -----Original Message-----
> From: Pali Rohár [mailto:pali.rohar@...il.com]
> Sent: Monday, October 2, 2017 6:53 AM
> To: Andy Shevchenko <andy.shevchenko@...il.com>
> Cc: Gabriel M. Elder <gabriel@...gnowsys.com>; Gabriele Mazzotta
> <gabriele.mzt@...il.com>; Limonciello, Mario <Mario_Limonciello@...l.com>;
> Darren Hart <dvhart@...radead.org>; Andy Shevchenko <andy@...radead.org>;
> platform-driver-x86@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: Re: keyboard backlight max_brightness bug on Dell Latitude E6410
> 
> On Friday 29 September 2017 18:19:59 Andy Shevchenko wrote:
> > >> FYI, latest update and info relating to
> > >> https://bugzilla.kernel.org/show_bug.cgi?id=196913
> >
> > Quick solution is to apply DMI to that.
> 
> It is only the Dell Latitude E6410 affected?
> 
> Mario, do you have any information about that API from Dell?
> 
> --
> Pali Rohár
> pali.rohar@...il.com

Pali,

I believe this particular API shouldn't have changed over generations, so it's 
likely something that needs to be quirked for that generation.  
I haven't had a chance to check on this yet in detail though.
For now could you guys quirk this one and if I find out there was something
more systemic we can undo the quirk and do something more broad.

Thanks,