linux-kernel - Re: Reporting bugs and bisection

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: <4804B5D5.4090404@davidnewall.com>
Date:	Tue, 15 Apr 2008 23:34:05 +0930
From:	David Newall <davidn@...idnewall.com>
To:	Michael Kerrisk <mtk.manpages@...il.com>
CC:	James Morris <jmorris@...ei.org>,
	Al Viro <viro@...iv.linux.org.uk>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Willy Tarreau <w@....eu>, david@...g.hm,
	Stephen Clark <sclark46@...thlink.net>,
	Evgeniy Polyakov <johnpol@....mipt.ru>,
	"Rafael J. Wysocki" <rjw@...k.pl>, Tilman Schmidt <tilman@...p.cc>,
	Valdis.Kletnieks@...edu, Mark Lord <lkml@....ca>,
	David Miller <davem@...emloft.net>, jesper.juhl@...il.com,
	yoshfuji@...ux-ipv6.org, jeff@...zik.org,
	linux-kernel <linux-kernel@...r.kernel.org>, git@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: Reporting bugs and bisection

Michael Kerrisk wrote:
> On 4/15/08, David Newall <davidn@...idnewall.com> wrote:
>   
>> James Morris wrote:
>>  > I don't know how to solve this, but suspect that encouraging the use of
>>  > reviewed-by and also including it in things like analysis of who is
>>  > contributing, selection for kernel summit invitations etc. would be a
>>  > start.  At least, better than nothing.
>>
>> Would it be hard to keep count of the number of errors introduced by
>>  author and reviewer?
>>     
>
> I've found quite a few errors in kernel-userland APIs, but I'm not
> sure that this sort of negative statistic would be helpful -- e.g.,
> more productive developers probably also introduce more errors.

We can already see which developers are more active.  What we can't see
is who is careless, which would be useful to know.  It would also be
useful to know who is careless in approving changes, because they share
responsibility for those changes.  It would be a good thing if this
highlighted that some people are behind frequent buggy changes.
--
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/