netdev - Re: [BUG] New Kernel Bugs

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20071113135658.5c9ac7ba.akpm@linux-foundation.org>
Date:	Tue, 13 Nov 2007 13:56:58 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jörn Engel <joern@...fs.org>
Cc:	Mark Lord <liml@....ca>, Ingo Molnar <mingo@...e.hu>,
	alsa-devel@...a-project.org, netdev@...r.kernel.org,
	linux-pcmcia@...ts.infradead.org, linux-kernel@...r.kernel.org,
	protasnb@...il.com, linux-ide@...r.kernel.org,
	bugme-daemon@...zilla.kernel.org,
	linux-input@...ey.karlin.mff.cuni.cz,
	David Miller <davem@...emloft.net>
Subject: Re: [BUG] New Kernel Bugs

On Tue, 13 Nov 2007 22:33:58 +0100 Jörn Engel <joern@...fs.org> wrote:

> On Tue, 13 November 2007 15:18:07 -0500, Mark Lord wrote:
> > 
> > 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 
> > machine,
> > and then I track it down, fix it, and submit the patch, generally all 
> > within a
> > couple of hours.  Where the heck was the dude(ess) that broke it ??  AWOL.
> > 
> > And when I receive hostility from the "maintainers" of said code for fixing
> > their bugs, well.. that really motivates me to continue reporting new ones..
> 
> 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.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html