From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [BUG] New Kernel Bugs Date: Tue, 13 Nov 2007 13:56:58 -0800 Message-ID: <20071113135658.5c9ac7ba.akpm@linux-foundation.org> References: <20071113031553.3c7b5c16.akpm@linux-foundation.org> <20071113.033946.114918709.davem@davemloft.net> <20071113034916.2556edd7.akpm@linux-foundation.org> <20071113.035824.40509981.davem@davemloft.net> <20071113041259.79c9a8c5.akpm@linux-foundation.org> <20071113134029.GA30978@elte.hu> <4739AFE0.20705@rtr.ca> <20071113193750.GD1356@flint.arm.linux.org.uk> <473A067F.3090007@rtr.ca> <20071113213358.GC20167@lazybastard.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20071113213358.GC20167@lazybastard.org> Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: =?ISO-8859-1?B?SvZybg==?= Engel Cc: Mark Lord , Ingo Molnar , alsa-devel@alsa-project.org, netdev@vger.kernel.org, linux-pcmcia@lists.infradead.org, linux-kernel@vger.kernel.org, protasnb@gmail.com, linux-ide@vger.kernel.org, bugme-daemon@bugzilla.kernel.org, linux-input@atrey.karlin.mff.cuni.cz, David Miller List-Id: linux-input@vger.kernel.org On Tue, 13 Nov 2007 22:33:58 +0100 J=F6rn Engel wrote: > On Tue, 13 November 2007 15:18:07 -0500, Mark Lord wrote: > >=20 > > I just find it weird that something can be known broken for several -rc* > > kernels before I happen to install it, discover it's broken on my own=20 > > machine, > > and then I track it down, fix it, and submit the patch, generally all=20 > > within a > > couple of hours. Where the heck was the dude(ess) that broke it ?? AW= OL. > >=20 > > And when I receive hostility from the "maintainers" of said code for fi= xing > > their bugs, well.. that really motivates me to continue reporting new o= nes.. >=20 > Given a decent bug report, I agree that having the bug not looked at is > shameful. But what can a developer do if a bug report effectively reads > "there is some bug somewhere in recent kernels"? How can I know that in > this particular case it is my bug that I introduced? It could just as > easily be 50 other people and none of them are eager to debug it unless > they suspect it to be their bug. It's relatively common that a regression in subsystem A will manifest as a failure in subsystem B, and the report initially lands on the desk of the subsystem B developers. But that's OK. The subsystem B people are the ones with the expertise to be able to work out where the bug resides and to help the subsystem A people understand what went wrong. Alas, sometimes the B people will just roll eyes and do nothing because they know the problem wasn't in their code. Sometimes.