linux-kernel - Re: Touchpad multitouch leaves ghost fingers

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: <CAEU-x4mJiBM_zKg1DaeJkKB3W3Ay08bUTc-D3QjFjDxNiZGd0g@mail.gmail.com>
Date: Mon, 22 Sep 2025 23:32:07 +0300
From: Yinon Burgansky <yinonburgansky@...il.com>
To: Benjamin Tissoires <bentiss@...nel.org>
Cc: jikos@...nel.org, linux-input@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: Touchpad multitouch leaves ghost fingers

On Mon, Sep 22, 2025 at 7:51 PM Benjamin Tissoires <bentiss@...nel.org> wrote:
> Well, I was meaning that I would provide a HID-BPF MR ready to install
> for you.
That would be awesome! Thank you very much!

> But if you want to play with it, feel free to do so :)
> For a jump start on HID-BPF:
> https://libevdev.pages.freedesktop.org/udev-hid-bpf/tutorial.html
Thank you for the reference. I’m feeling quite fatigued from the
debugging process, as it took me a considerable amount of time to
identify the issue.
It was surprisingly difficult to determine what exactly was wrong with
the touchpad and to uncover the root cause; perhaps I didn’t search
for the right terms.
However, I’m glad I finally took the time to debug it, submit the bug
report, and find out what was wrong. Thank you!

> The advantage of HID-BPF is that we can drop the file in the filesystem
> and then forget about it.
> My plan is to have the HID-BPF detect whether the quirk has been applied
> or not and would gracefully remove itself once the kernel is fixed.
That's cool, nice design.

> PS: please try to refrain from top-posting your reply. The usage is to
> inline your reply or reply below,
Sorry about that, hopefully I did it right this time.

Thanks,
Yinon