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

[Neil Horman]

On Tue, Jul 15, 2008 at 01:51:17PM +0200, Ingo Molnar wrote:
> 
> * Ingo Molnar <mingo@xxxxxxx> wrote:
> 
> > 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.
> 
> here's the band-aid patch i'm using.
> 
> 	Ingo
> 
> -------------->
> commit 3fdcd29e5c272c66424ac7616fcd4a9a725bc206
> Author: Ingo Molnar <mingo@xxxxxxx>
> Date:   Tue Jul 15 13:34:15 2008 +0200
> 
>     crypto: exclude broken CRYPTO_PRNG code
>     
>     Signed-off-by: Ingo Molnar <mingo@xxxxxxx>
> ---
>  crypto/Kconfig |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/crypto/Kconfig b/crypto/Kconfig
> index ea50357..2cf66ca 100644
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -670,6 +670,8 @@ comment "Random Number Generation"
>  
>  config CRYPTO_PRNG
>  	tristate "Pseudo Random Number Generation for Cryptographic modules"
> +	# causes bootup crashes with config-Tue_Jul_15_10_35_22_CEST_2008.bad
> +	depends on 0
>  	help
>  	  This option enables the generic pseudo random number generator
>  	  for cryptographic modules.  Uses the Algorithm specified in

Who's using this at the moment Ingo? its part of a larger effort for pseudo
random initial vectors for ipsec.  Nothing should depend on or load this module
yet, let alone alloc a context.

Not that that forgives the oops (which incidentally doesn't occur on my systems,
since I build with CRYPTO_CTR enabled).

The patch to fix this is trivial, I'll be posting it later today, after I test
it.

Neil

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