6a0fcbb4da
If we have at least one algorithm built-in then it no longer makes sense to have the testing framework, and hence cryptomgr to be a module. It should be either on or off, i.e., built-in or disabled. This just happens to stop a potential runaway modprobe loop that seems to trigger on at least one distro. With fixes from Evgeniy Polyakov. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> |
||
---|---|---|
.. | ||
async_tx | ||
Kconfig | ||
Makefile | ||
ablkcipher.c | ||
aead.c | ||
aes_generic.c | ||
ahash.c | ||
algapi.c | ||
algboss.c | ||
ansi_cprng.c | ||
anubis.c | ||
api.c | ||
arc4.c | ||
authenc.c | ||
blkcipher.c | ||
blowfish.c | ||
camellia.c | ||
cast5.c | ||
cast6.c | ||
cbc.c | ||
ccm.c | ||
chainiv.c | ||
cipher.c | ||
compress.c | ||
crc32c.c | ||
cryptd.c | ||
crypto_null.c | ||
ctr.c | ||
cts.c | ||
deflate.c | ||
des_generic.c | ||
digest.c | ||
ecb.c | ||
eseqiv.c | ||
fcrypt.c | ||
fips.c | ||
gcm.c | ||
gf128mul.c | ||
hash.c | ||
hmac.c | ||
internal.h | ||
khazad.c | ||
krng.c | ||
lrw.c | ||
lzo.c | ||
md4.c | ||
md5.c | ||
michael_mic.c | ||
pcbc.c | ||
proc.c | ||
ripemd.h | ||
rmd128.c | ||
rmd160.c | ||
rmd256.c | ||
rmd320.c | ||
rng.c | ||
salsa20_generic.c | ||
scatterwalk.c | ||
seed.c | ||
seqiv.c | ||
serpent.c | ||
sha1_generic.c | ||
sha256_generic.c | ||
sha512_generic.c | ||
tcrypt.c | ||
tcrypt.h | ||
tea.c | ||
testmgr.c | ||
testmgr.h | ||
tgr192.c | ||
twofish.c | ||
twofish_common.c | ||
wp512.c | ||
xcbc.c | ||
xor.c | ||
xts.c |