On Sat, Jun 06, 2015 at 04:20:35AM +0200, Stephan Mueller wrote: > When compiling the DRBG statically into the kernel, the testmgr > allocation of the DRBG may be done at a time the Jitter RNG is > not available. The testmgr instantiates a number of DRBGs for performing > testing which may cause a flurry of logs about unavailable Jitter RNG. > Note, the Jitter RNG is not needed for the testmgr operation anyways.
I think we should fix by ensuring the jitter is registered first. You could try registering jitter at subsys_init instead of module_init. Cheers, -- Email: Herbert Xu <herb...@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
