linux-kernel - Re: [RFC: 2.6 patch] let GROUP

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, 27 May 2008 20:53:36 +0300
From:	Adrian Bunk <bunk@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Mike Galbraith <efault@....de>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [RFC: 2.6 patch] let GROUP_SCHED depend on BROKEN

On Tue, May 27, 2008 at 04:22:12PM +0200, Ingo Molnar wrote:
>...
> To make sure i'm accurate about this i just spent 15 minutes
> reviewing all your past commits to the Linux kernel using
> "git-shortlog --author=Bunk", and the rather sobering truth
> appears to be that:
> 
>   - you've _never_ before fixed a complex Linux kernel bug/problem

What is a "complex kernel problem"?

Just looking a bit through the last month:

E.g. http://lkml.org/lkml/2008/5/14/498 was not horribly complex, but 
for 3 days noone else had bothered to answer the request of the driver 
maintainer for help with this regression.

As you yourself said http://article.gmane.org/gmane.linux.kernel/676733
is something where I spotted a real bug just by reading through patches 
on linux-kernel. The bug might or might not have been complex, but since 
someone spotted it just when reading through patches (it's entirly 
possible someone else might have spotted it as well, but we will never 
know for sure) it never became a bug in any tree.

And for me stuff like http://lkml.org/lkml/2008/4/28/561 isn't complex, 
but quite frankly my impression is that I'm currently one out of only 
two people understanding our Kconfig files good enough for fixing such 
stuff.

>   - you've never before written a _single_ Linux kernel feature
>   - you've never before written a _single_ Linux driver

True.

I am not a coder.
I am just a cleanup and QA guy.

I know that this makes me a persona non grata for some people on this 
list, but I prefer doing what I'm good at (bugfixes and cleanup
patches, aiming at not introducing new bugs) over doing what I'm
bad at (writing code).

>   - you've never before done any true self-driven functional 
>     changes/improvements to Linux

I'd claim having started regression tracking (which was 100% self-driven)
was a functional improvement for Linux kernel development - and I don't 
care that you disagree on this.

>...
> 	Ingo

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
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/