From: Jiri Kosina <firstname.lastname@example.org>
To: Benjamin Tissoires <email@example.com>
Cc: "Linus Torvalds" <firstname.lastname@example.org>,
"Linux regressions mailing list" <email@example.com>,
"Bagas Sanjaya" <firstname.lastname@example.org>,
"Filipe Laíns" <email@example.com>,
"Bastien Nocera" <firstname.lastname@example.org>,
"open list:HID CORE LAYER" <email@example.com>,
Subject: Re: [regression] Since kernel 6.3.1 logitech unify receiver not working properly
Date: Fri, 26 May 2023 20:41:12 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.firstname.lastname@example.org> (raw)
On Thu, 25 May 2023, Jiri Kosina wrote:
> > > > That bug is pre-existing (ie the problem was not introduced by that
> > > > commit), but who knows if the retry makes things worse (ie if it then
> > > > triggers on a retry, the response data will be the *previous* response).
> > > >
> > > > The whole "goto exit" games should be removed too, because we're in a
> > > > for-loop, and instead of "goto exit" it should just do "break".
> > > >
> > > > IOW, something like this might be worth testing.
> > > >
> > > > That said, while I think the code is buggy, I doubt this is the actual
> > > > cause of the problem people are reporting. But it would be lovely to
> > > > hear if the attached patch makes any difference, and I think this is
> > > > fixing a real - but unlikely - problem anyway.
> > FWIW, Linus, your patch is
> > Reviewed-by: Benjamin Tissoires <email@example.com>
> > Feel free to submit it to us or to apply it directly if you prefer as
> > this is clearly a fix for a code path issue.
> It would be nice to hear from the people who were able to reproduce the
> issue whether this makes any observable difference in behavior though. I
> don't currently think it would, as it fixes a potential NULL pointer
> dereference, which is not what has been reported.
> Has anyone of the affected people tried to bisect the issue?
Could anyone who is able to reproduce the issue please check whether
586e8fede7953b16 ("HID: logitech-hidpp: Retry commands when device is busy")
has any observable effect?
next prev parent reply other threads:[~2023-05-26 18:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 9:55 [regression] Since kernel 6.3.1 logitech unify receiver not working properly Linux regression tracking (Thorsten Leemhuis)
2023-05-11 11:58 ` Thorsten Leemhuis
2023-05-16 13:24 ` Bagas Sanjaya
2023-05-16 13:34 ` Benjamin Tissoires
2023-05-22 12:38 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 18:23 ` Linus Torvalds
2023-05-23 12:31 ` Jiri Kosina
2023-05-24 15:27 ` Benjamin Tissoires
2023-05-25 11:10 ` Jiri Kosina
2023-05-25 11:19 ` Benjamin Tissoires
2023-05-26 18:41 ` Jiri Kosina [this message]
2023-05-28 12:21 ` Thorsten Leemhuis
2023-05-31 8:43 ` Jiri Kosina
2023-05-31 8:46 ` Bastien Nocera
2023-05-16 13:53 ` Thorsten Leemhuis
2023-05-17 13:17 ` Bagas Sanjaya
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.