linux-kernel - Re: [PATCH] return hidden bug

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:	Tue, 23 Oct 2007 02:15:01 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Ray Lee <ray-lk@...rabbit.org>
CC:	Roel Kluin <12o3l@...cali.nl>, Rik van Riel <riel@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] return hidden bug

On 10/23/2007 01:00 AM, Ray Lee wrote:

> On 10/22/07, Rene Herman <rene.herman@...access.nl> wrote:

>> Hugely trust inspiring isn't it -- the amount of eyes and comments you'll
>> get even on trivial patches like this? This development model is working!
> 
> Go easy with the snarkiness, hmm? It's the trivial ones that seem to
> be the most dangerous. The larger ones actually get *tested*
> sometimes.

I was also commenting and don't generally on anything much more involved so 
any snarkiness included myself which should make things better.

>> Now if only we'd sometimes get some for non trivial patches as well...
> 
> That's certainly true regardless, but for myself, I'd rather throw
> some reviews out for the small ones since I have adequate time and
> knowledge for them. The larger ones require domain specific knowledge
> I lack, and time I don't have.

Exactly the problem. Comment was mostly triggered due to me looking at a 
problem with a proprietary CD-ROM driver again tonight that I posted a few 
months ago where the only comment has been from the fellow author. There the 
problem was the block layer blowing up and given that it seems unlikely that 
this wouldn't be a problem inside the newbie-driver itself, that the block 
part of it was actually really small and people said they'd look at it, the 
subsequent thundering silence still annoys me.

Ofcourse, now it seems the kernel itself has moved on enough that the driver 
doesn't work at _all_ anymore and I at the moment lack the time to spend the 
required hours googling around trying to find out what the heck changed out 
from under me so that I might get it to at least do what it already did do.

Hey, I don't actually know and maybe I'm just wrong but I have the feeling 
that over the last 1 or 2 years most new developers seem to be either people 
that are payed to be so, perhaps in the form of graduation, or janitors. The 
kernel is much, much more complex than even only a few years ago and at the 
same time the number of knowledgeable developers who'll do something other 
than their own thing and otherwise just wait around for something perfect to 
merge seems to be approaching zero.

That is -- I do not feel that the current developer base is expending overly 
many efforts to appear welcoming.

Please feel free to do the open-source thing and argue that's actually an 
advantage (there we have that snarkiness again...) or otherwise ignore me. 
I'll just sit here and be grumpy anyway. Might be better after a good 
night's sleep...

Rene.

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