Re: BUG: unable to handle kernel NULL pointer dereference at000000000000000e (reset_prng_context)

From: Ingo Molnar
Date: Tue Jul 15 2008 - 07:33:44 EST



* Neil Horman <nhorman@xxxxxxxxxxxxx> wrote:

> On Tue, Jul 15, 2008 at 12:25:37AM +0100, Simon Arlott wrote:
> > http://img182.imageshack.us/img182/7205/1005489hh6.jpg
> >
> > .config attached
> >
> > --
> > Simon Arlott
>
> Looks like you don't have rfc3686(ctr(aes)) compiled in. Add
> CONFIG_CRYPTO_CTR to your config, IIRC. I'll add a depends directive
> to Kconfig for that in my next update.

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.

And the commit log says:

| commit b8454eebe380677789735fd6bad368af2e6b2d1e
| Author: Neil Horman <nhorman@xxxxxxxxxxxxx>
| AuthorDate: Mon Jul 7 22:41:31 2008 +0800
| CommitDate: Thu Jul 10 20:35:18 2008 +0800
|
| crypto: prng - Deterministic CPRNG

i.e. this patch went in just 7 days from development to upstream, with
insufficient review, with no linux-next presence at all (as of
linux-next when v2.6.26 was released) and insufficient testing.

That's not how it's supposed to be.

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/