linux-kernel - Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000000e (reset_prng

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, 15 Jul 2008 20:04:43 -0400
From:	Neil Horman <nhorman@...driver.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Alexey Dobriyan <adobriyan@...il.com>, davem@...emloft.net,
	mingo@...e.hu, simon@...e.lp0.eu, linux-kernel@...r.kernel.org,
	herbert@...dor.apana.org.au
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at
	000000000000000e (reset_prng_context)

On Tue, Jul 15, 2008 at 03:11:10PM -0700, Andrew Morton wrote:
> On Wed, 16 Jul 2008 01:49:30 +0400
> Alexey Dobriyan <adobriyan@...il.com> wrote:
> 
> > On Tue, Jul 15, 2008 at 01:44:07PM -0700, David Miller wrote:
> > > From: Ingo Molnar <mingo@...e.hu>
> > > 
> > > > i have just triggered this crash too. Please, when you know about bootup 
> > > > crashes in your code send a patch to the lkml thread so that people can 
> > > > apply it and have a working system.
> > > > 
> > > > Note that the new crypto/prng.c driver has very bad quality:
> > > > 
> > > >   total: 45 errors, 21 warnings, 1 checks, 410 lines checked
> > > > 
> > > > It has tons of completely unacceptable code mistakes in it.
> > > 
> > > I think we should merge new drivers as aggressively as possible.
> > 
> > Well, I don't have strong opinion about this exact statement, but
> > 
> > 	Ingo, COULD YOU PLEASE PERSONALLY FUCKING STOP THIS
> > 	CHECKPATCH.PL-AS-INDICATOR HORSESHIT !
> 
> Well I wouldn't put it that way but sure, there is no clear correlation.
> 
> Except that such a high density of coding-style errors is an indication
> that the code was not closely and critically reviewed by an experienced
> kernel developer.
> 
In fairness, I should have run checkpatch.pl on it before I submitted (sorry,
I'm bad about that), and I just missed the bad ifdef check for my startup test,
because I never thought to test with CRYPTO_PRNG built monolithically and no
support for the requisite cipher built in.  That was just stupid of of me, and I
apologize.

As its been pointed out though, these are trivial errors, and as such trivial to
fix (FWIW, the 45 errors from checkpatch boiled down to all spacing on about 10
different lines of code).   The PRNG works, is usefull, and for anything that
doesn't use it its irrelevant (now that it doesn't oops when built in).

At any rate, its all moot now anyway, I've posted patches that clean up the
whitespace, and fix the oops.  

Regards
Neil

-- 
/****************************************************
 * Neil Horman <nhorman@...driver.com>
 * Software Engineer, Red Hat
 ****************************************************/
--
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/