linux-kernel - Re: [PATCH AUTOSEL 4.18 094/131] Input: atmel_mxt_ts

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:   Wed, 5 Sep 2018 10:14:59 -0700
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     Alexander.Levin@...rosoft.com
Cc:     "3.8+" <stable@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>,
        Nick Dyer <nick.dyer@...ev.co.uk>
Subject: Re: [PATCH AUTOSEL 4.18 094/131] Input: atmel_mxt_ts - only use first
 T9 instance

On Sun, Sep 2, 2018 at 6:05 AM Sasha Levin
<Alexander.Levin@...rosoft.com> wrote:
>
> From: Nick Dyer <nick.dyer@...ev.co.uk>
>
> [ Upstream commit 36f5d9ef26e52edff046b4b097855db89bf0cd4a ]
>
> The driver only registers one input device, which uses the screen
> parameters from the first T9 instance. The first T63 instance also uses
> those parameters.
>
> It is incorrect to send input reports from the second instances of these
> objects if they are enabled: the input scaling will be wrong and the
> positions will be mashed together.
>
> This also causes problems on Android if the number of slots exceeds 32.
>
> In the future, this could be handled by looking for enabled touch object
> instances and creating an input device for each one.

So if this is proposed for stable, how many devices are actually
affected by this? Why does this need to be in stable?

Thanks.

-- 
Dmitry