Re: Initcall ordering problem (TTY vs modprobe vs MD5) and cryptomgr problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Aug 06, 2010 at 02:01:03AM +0100, David Howells wrote:
> 
> but it's not being found by the crypto routines.  By GIT bisection, I note
> that this problem is introduced in the following commit:
> 
> 	commit 0b767f96164b2b27488e3daa722ff16e89d49314
> 	Author: Alexander Shishkin <virtuoso@xxxxxxxxx>
> 	Date:   Thu Jun 3 20:53:43 2010 +1000
> 
> 	crypto: testmgr - add an option to disable cryptoalgos' self-tests

Indeed this changeset is buggy.  It makes cryptomgr return a value
as if it was not loaded.  This triggers the module load.

I'll send you a patch.

Thanks,
-- 
Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux