linux-kernel - Re: Article in Phoronix about loss of performance in 2.6.35 release candidates

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]

Date:	Tue, 1 Jun 2010 08:25:40 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Pekka Enberg <penberg@...helsinki.fi>,
	Alexander Viro <viro@....linux.org.uk>
Cc:	tytso@....edu, Alex Buell <alex.buell@...ted.org.uk>,
	Mailing Lists - Kernel Developers 
	<linux-kernel@...r.kernel.org>, Eric Paris <eparis@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: Article in Phoronix about loss of performance in 2.6.35 release
 candidates

* Ingo Molnar <mingo@...e.hu> wrote:

> Is lacking pretty much all essential pieces of information which are 
> required for reverts:
> 
>  - it has no description about who reported the bug.

In fact it was _bisected_ by Eric Paris, so a Bisected-by tag is a must.

Eric is a nice guy and i'm sure wont complain about this, but i can tell it 
with a 100% certainty that to most testers and developers bisecting bugs is a 
tiresome and error-prone process that involves quite a bit of work.

Bisecting a bug is often more work to do than the work which went into the 
original commit and the revert, combined.

So if we want more people to test our commits then the least we can do is to 
credit testers by making proper use of the Reported-by and Bisected-by tags.

	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/