linux-kernel - Re: PROBLEM: Regression likely in hid_uclogic driver breaks Huion Inspiroy H640 drawing tablet

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: <20220727162755.GA3839@elementary>
Date:   Wed, 27 Jul 2022 18:27:55 +0200
From:   José Expósito <jose.exposito89@...il.com>
To:     Stefan Hansson <newbie13xd@...il.com>
Cc:     Jiri Kosina <jikos@...nel.org>,
        Benjamin Tissoires <benjamin.tissoires@...hat.com>,
        Ping Cheng <ping.cheng@...om.com>,
        Peter Hutterer <peter.hutterer@...-t.net>,
        linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: Regression likely in hid_uclogic driver breaks Huion
 Inspiroy H640 drawing tablet

On Tue, Jul 26, 2022 at 10:56:33PM -0400, Stefan Hansson wrote:
> Hi!
> 
> > > Thanks for looking into this! Bisecting has been slow on my end
> > > unfortunately. I built today's linux-next (20220726) with your proposed
> > > patch below and my drawing tablet curiously still does not work as expected.
> > > The stylus works a couple of times, but eventually stops working (unlike
> > > prior where it always seemed to only work once). Do I need both your revert
> > > and this diff for it to work properly?
> > 
> > You are right, I just tested for a while with the diff applied (without
> > reverting the commit causing the issue) and after putting the pen in
> > and out proximity a fair amount of times (> 100) it stopped working.
> 
> This part is peculiar to me. When I said "a couple of times", I really meant
> a couple of times. For me, this issue reproduces after maybe 10 times at
> most. I have never been able to do it for anything close to 100 times. I
> wonder what's up with this disparity?

We are most likely doing something different. Anyway, the important bit
is that with the current code present 5.18 the bug is easy to reproduce
in order to test fixes.

Jose