* Herbert Xu | 2007-10-05 23:10:51 [+0800]: >BTW, the dead-lock does exist after all. The lock that's held >is the user-space file lock held by modprobe. Assuming that >padlock-sha comes before sha in the alias list, then the second >modprobe will hit padlock-sha again and dead-lock. I tried to deadlock and I did not succeed, maybe I did something wrong. # fgrep sha modules.alias alias sha256 padlock_sha alias sha1 padlock_sha alias sha384 sha512 alias sha256 sha256_generic alias sha1 sha1_generic padlock comes first as you said. A "modprobe tcrypt mode=2" worked fine (with the test passed). # lsmod |grep sha sha1_generic 3008 0 padlock_sha 4160 0 crypto_algapi 13824 4 sha1_generic,padlock_sha,blkcipher,cryptomgr I have a version of the padlock-sha driver with no HW dependency (fallback only, that one I used) at git://git.breakpoint.cc/bigeasy/linux via_sha if you want to test :) >Cheers, Sebastian - 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
