linux-kernel - Re: Fwd: Logitech G915 Wireless Keyboard acts weird on 6.6.0

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:   Tue, 21 Nov 2023 14:37:52 +0100 (CET)
From:   Jiri Kosina <jikos@...nel.org>
To:     Bagas Sanjaya <bagasdotme@...il.com>
cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Input Devices <linux-input@...r.kernel.org>,
        Thorsten Leemhuis <regressions@...mhuis.info>,
        Mavroudis Chatzilazaridis <mavchatz@...tonmail.com>,
        Filipe Laíns <lains@...eup.net>,
        Bastien Nocera <hadess@...ess.net>,
        LinuxCat <masch77.linuxcat@...il.com>,
        Marcelo <mmbossoni@...il.com>, Takashi Iwai <tiwai@...e.de>,
        Hans de Goede <hdegoede@...hat.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Fwd: Logitech G915 Wireless Keyboard acts weird on 6.6.0

On Tue, 21 Nov 2023, Bagas Sanjaya wrote:

> Hi Thorsten and all,
> 
> On Thu, Nov 02, 2023 at 09:11:42PM +0700, Bagas Sanjaya wrote:
> > Hi,
> > 
> > I notice a regression report on Bugzilla [1]. Quoting from it:
> > 
> > > Hello,
> > > After upgrading from 6.5.9 to 6.6.0, my keyboard started acting really weird in its wireless mode, key actions sent are completely wrong, see video attached. 
> > > 
> > > Most keys are perceived as either E, 3 or F7, with F8 and <, as well. 
> > > 
> > > Modifier keys (CTRL, ALT, ALT GR, Shift and Super) are working normally, as well as media control keys (pause/play, previous, next, mute and sound up/down).
> > > 
> > > The keyboard works as expected if it's wired.
> > 
> > Another reporter bisected the regression:
> > 
> > > Bisected to 
> > > 
> > > 9d1bd9346241cd6963b58da7ffb7ed303285f684 is the first bad commit
> > > commit 9d1bd9346241cd6963b58da7ffb7ed303285f684
> > > Author: Mavroudis Chatzilazaridis <mavchatz@...tonmail.com>
> > > Date: Sun Jul 16 18:23:44 2023 +0000
> > > 
> > > HID: logitech-dj: Add support for a new lightspeed receiver iteration
> > > 
> > > The lightspeed receiver for the Pro X Superlight uses 13 byte mouse reports
> > > without a report id. The workaround for such cases has been adjusted to
> > > handle these larger packets.
> > > 
> > > The device now reports the status of its battery in wireless mode and
> > > libratbag now recognizes the device and it can be configured with Piper.
> > > 
> > > https://github.com/libratbag/libratbag/pull/1122
> > > 
> > > Co-developed-by: Filipe Laíns <lains@...eup.net>
> > > Signed-off-by: Filipe Laíns <lains@...eup.net>
> > > Signed-off-by: Mavroudis Chatzilazaridis <mavchatz@...tonmail.com>
> > > Reviewed-by: Bastien Nocera <hadess@...ess.net>
> > > Signed-off-by: Jiri Kosina <jkosina@...e.cz>
> > > 
> > > drivers/hid/hid-ids.h | 1 +
> > > drivers/hid/hid-logitech-dj.c | 11 ++++++++---
> > > 2 files changed, 9 insertions(+), 3 deletions(-)
> > 
> > See Bugzilla for the full thread.
> > 
> > Anyway, I'm adding this regression to regzbot:
> > 
> > #regzbot introduced: 9d1bd9346241cd https://bugzilla.kernel.org/show_bug.cgi?id=218094
> > #regzbot title: Logitech G915 Wireless Keyboard key event only detects few key codes
> > #regzbot link: https://streamable.com/ac6l8u
> > 
> 
> There's no reply from culprit author nor linux-input people (did they miss
> this regression?). And on Bugzilla, other reporters replied that reverting
> the culprit fixed the regression.
> 
> FYI, there's similar Bugzilla report on [1].

As there was no reaction from Mavroudis in order to figure out why he is 
not observing the issues the other reporters do and what to do to fix 
those, I already do have revert in my queue for -rc3.

My first guess would be that the extra buttons in the extended report are 
not properly reflected in the emulated report descriptor, but that 
wouldn't explain why it worked for the author of the commit.

So revert it is, and once Marvoudis resurfaces, we can try again for some 
of later releases.

-- 
Jiri Kosina
SUSE Labs