![]() With the mandatory algorithm testing at registration, we have now created a deadlock with algorithms requiring fallbacks. This can happen if the module containing the algorithm requiring fallback is loaded first, without the fallback module being loaded first. The system will then try to test the new algorithm, find that it needs to load a fallback, and then try to load that. As both algorithms share the same module alias, it can attempt to load the original algorithm again and block indefinitely. As algorithms requiring fallbacks are a special case, we can fix this by giving them a different module alias than the rest. Then it's just a matter of using the right aliases according to what algorithms we're trying to find. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> |
||
---|---|---|
.. | ||
aes_s390.c | ||
crypt_s390.h | ||
crypto_des.h | ||
des_check_key.c | ||
des_s390.c | ||
Makefile | ||
prng.c | ||
sha.h | ||
sha1_s390.c | ||
sha256_s390.c | ||
sha512_s390.c | ||
sha_common.c |