linux-kernel - Re: [Bug #10117] 2.6.25-current-git sometimes hangs on boot -dual-core Sony Vaio

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] [day] [month] [year] [list]

Date:	Wed, 16 Apr 2008 02:50:36 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>,
	Soeren Sonnenburg <kernel@....de>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Mark Lord <lkml@....ca>
Subject: Re: [Bug #10117] 2.6.25-current-git sometimes hangs on boot
	-dual-core Sony Vaio

* Adrian Bunk <bunk@...nel.org> wrote:

> On Tue, Apr 15, 2008 at 07:54:11PM -0300, Carlos R. Mafra wrote:
> > On Wed 16.Apr'08 at  0:29:49 +0300, Adrian Bunk wrote:
> >...
> > > We must learn to more aggressively point people at reporting their 
> > > issues in own bugs, instead of hijacking an already existing similar
> > > looking bug (that might be for a different issue).
> > 
> > I understand now, but you made me feel bad about it.
> 
> Sorry for my wording, it was not meant personally.
> 
> It's a general problem in bug trackers that one person reports one 
> issue, and other people say "I have the same bug" and start discussing 
> their problem, which might or might not turn out to be the same.

... which you should realize that this is generally a _GOOD_ thing. This 
whole Linux thing is about doing things in a group, not about doing 
things separately. It permeates everything and it's our main strength.

Analogously to nuclear fission and to torrent streams, bug handling 
needs a "critical mass" as well - the more testers, the better. (even if 
they end up having different issues)

So i'd rather see bugs being mistakenly handled together (they are easy 
to separate out once they are established to be separate) than the same 
bug being processed on two different tracks.

Your rigid, buerocratic view of this matter is wrong, harmful and it 
actively discourages testers. Please stop it.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/