On 16.05.23 15:24, Bagas Sanjaya wrote: > On 5/11/23 18:58, Thorsten Leemhuis wrote: >> Hi, Thorsten here, the Linux kernel's regression tracker. >> >> On 08.05.23 11:55, Linux regression tracking (Thorsten Leemhuis) wrote: >>> Hi, Thorsten here, the Linux kernel's regression tracker. >>> >>> I noticed a regression report in bugzilla.kernel.org. As many (most?) >>> kernel developers don't keep an eye on it, I decided to forward it by mail. >>> >>> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217412 : >> >> TWIMC: a few other users (three or four iirc) showed up in that ticket >> and reported problems with the receiver, albeit the symptoms are not >> exactly the same for all of them, so there might be more than one problem. >> >> I'll try to motivate the affected users to perform a bisection. But >> would be great if those with more knowledge about this code could >> briefly look into the ticket, maybe the details the users shared allows >> one of you to guess what causes this. > > Hmm, > > You noted in the similar report [1] that developers involved here > ignore this regressions. I wonder if Linus has to be hired in > this case, and if it is the case, let's take a look and hear closely what > he will say. > > [1]: https://lore.kernel.org/regressions/8941c5f2-3861-da68-06ca-adc68a37e53b@xxxxxxxxxxxxx/ You CCed him so maybe we'll learn soon. I expect he doesn't like the situation, but at the same time I guess there is nothing much he will do (which is why I do not CC him in cases like this, unless they are urgent/severe or something like that). That's because as far as I know in the end it is the duty of the reporter(s) to find the the culprit. Because in the end developers and subsystem maintainers are volunteers, too -- and making them bisect each and every report would make the job way to hard. And the question "which developer/subsystem maintainer needs to perform the bisection" would often become quickly complicated as well, as an issue in one area of the kernel can be caused by a change in a totally different area (for file-systems that is way more likely than for input drivers, but still). Not to mention that developer and subsystem maintainers might not even have the environment at hand to reproduce the issue. That being said: I think a quick "We looked into these three reports that might be related, but we have no idea what might cause this; somebody needs to bisect things" from one of the involved developers/maintainers would have been nice (appropriate?). Ciao, Thorsten
