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
| ||
|
Message-ID: <YzsG2uC70WfawKTs@pendragon.ideasonboard.com> Date: Mon, 3 Oct 2022 18:59:22 +0300 From: Laurent Pinchart <laurent.pinchart@...asonboard.com> To: Steven Rostedt <rostedt@...dmis.org> Cc: Thorsten Leemhuis <linux@...mhuis.info>, Slade Watkins <srw@...dewatkins.net>, Konstantin Ryabitsev <konstantin@...uxfoundation.org>, "Artem S. Tashkinov" <aros@....com>, workflows@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>, ksummit@...ts.linux.dev Subject: Re: Planned changes for bugzilla.kernel.org to reduce the "Bugzilla blues" On Mon, Oct 03, 2022 at 11:51:02AM -0400, Steven Rostedt wrote: > On Mon, 3 Oct 2022 18:44:45 +0300 Laurent Pinchart wrote: > > > > The sad part is that most people that are going to report a bug is not > > > going to read a full document to figure out how to do it. Usually when > > > someone hits a bug, they are doing something else. And it's a burden to > > > report it. Obviously, they want it to be fixed, but it's viewed as a favor > > > to the developer and not the user to get it fixed, as it's likely seen as a > > > mistake by the developer that the bug exists in the first place. > > > > It really depends on how badly the bug affects the reporter. I'm sure > > that a bug that prevents GPU or audio from working alone on a shiny > > brand new laptop will see lots of pings. A side issue noticed by the > > user that wouldn't really affect them is more likely to end up in a > > blackhole. I recently faced issues with a display controller. I sent > > patches for the problems affecting my use case, and only notified the > > maintainer for the other issues. Those have been "added to their todo > > list (TM)". But is that really a problem ? If I'm not affected and > > neither is the maintainer, there's likely better use of their time, at > > least until a user who is really affected by the problem shows up. > > I guess that's the main question. If we see hundreds of bugzilla reports > ignored, are they the one offs that nobody really cares about, or are they > the ones where it's preventing someone from using their new laptop properly? > > Sometimes, even if it prevents a laptop from working properly, it could be > ignored if a workaround is in place. Like just buying an external webcam if > you can't get the internal one working. That's an interesting example. https://lwn.net/Articles/904776/ shows how it made lots of users *very* unhappy. -- Regards, Laurent Pinchart
Powered by blists - more mailing lists