|From:||David Miller <davem-AT-davemloft.net>|
|Subject:||Re: [BUG] New Kernel Bugs|
|Date:||Tue, 13 Nov 2007 04:32:07 -0800 (PST)|
|Cc:||protasnb-AT-gmail.com, linux-kernel-AT-vger.kernel.org, netdev-AT-vger.kernel.org, alsa-devel-AT-alsa-project.org, linux-ide-AT-vger.kernel.org, linux-pcmcia-AT-lists.infradead.org, linux-input-AT-atrey.karlin.mff.cuni.cz, bugme-daemon-AT-bugzilla.kernel.org|
From: Andrew Morton <email@example.com> Date: Tue, 13 Nov 2007 04:12:59 -0800 > On Tue, 13 Nov 2007 03:58:24 -0800 (PST) David Miller <firstname.lastname@example.org> wrote: > > > From: Andrew Morton <email@example.com> > > Date: Tue, 13 Nov 2007 03:49:16 -0800 > > > > > Do you believe that our response to bug reports is adequate? > > > > Do you feel that making us feel and look like shit helps? > > That doesn't answer my question. > > See, first we need to work out whether we have a problem. If we do this, > then we can then have a think about what to do about it. > > I tried to convince the 2006 KS attendees that we have a problem and I > resoundingly failed. People seemed to think that we're doing OK. > > But it appears that data such as this contradicts that belief. > > This is not a minor matter. If the kernel _is_ slowly deteriorating then > this won't become readily apparent until it has been happening for a number > of years. By that stage there will be so much work to do to get us back to > an acceptable level that it will take a huge effort. And it will take a > long time after that for the kerel to get its reputation back. > > So it is important that we catch deterioration *early* if it is happening. You tell me what I should spend my time working on, and I promise to do it OK? :-) For example, if I have a choice between a TCP crash just about anyone can hit and some obscure issue only reported with some device nearly nobody has, which one should I analyze and work on? That's the problem. All of us prioritize and it means the chaff collects at the bottom. You cannot fix that except by getting more bug fixers so that the chaff pile has a chance to get smaller. Luckily if the report being ignored isn't chaff, it will show up again (and again and again) and this triggers a reprioritization because not only is the bug no longer chaff, it also now got a lot of information tagged to it so it's a double worthwhile investment to work on the problem. I think a lot of bugs that "aren't getting looked at" are simply sitting in some early stage of this process.
Copyright © 2007, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds