linux-kernel - Re: [PATCH 4.10 54/62] Input: i8042 - add Clevo P650RS to the i8042 reset list

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]

Date:   Tue, 2 May 2017 12:16:18 +1000
From:   Ed Bordin <edbordin@...il.com>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Paweł Bylica <chfast@...il.com>
Subject: Re: [PATCH 4.10 54/62] Input: i8042 - add Clevo P650RS to the i8042
 reset list

On 2 May 2017 at 11:22, Dmitry Torokhov <dmitry.torokhov@...il.com> wrote:
> On May 1, 2017 6:14:54 PM PDT, Ed Bordin <edbordin@...il.com> wrote:
>>On 2 May 2017 at 07:35, Greg Kroah-Hartman <gregkh@...uxfoundation.org>
>>wrote:
>>> 4.10-stable review patch.  If anyone has any objections, please let
>>me know.
>>
>>Minor query (that I probably should have raised earlier): is there any
>>data to support the comment that the DMI_PRODUCT_NAME "P65xRP" matches
>>all of "P650RS, 650RP6, Sager NP8152-S"? I have only tested on a
>>P650RP variant.
>
> I pulled the product names from dmi data from the Launchpad bug referenced in bugzilla.
>
>
> Thanks.
>
> --
> Dmitry

I guess what I was getting at is that it seemed a little odd that the
RS variant from the original bug report would only have "RP" in its
product string. Just did some more digging and it looks like
DMI_PRODUCT_NAME for the RS model in the original bug report is
"P65_67RSRP" [1] but we probably have no way of testing it unless
Paweł Bylica or someone else is able to help.

Don't get me wrong, I'm happy if this goes through as-is! But thought
it would be best to note that in case it causes any future confusion.

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1645322