• A
    security/keys: BIG_KEY requires CONFIG_CRYPTO · 3cd18d19
    Arnd Bergmann 提交于
    The recent rework introduced a possible randconfig build failure
    when CONFIG_CRYPTO configured to only allow modules:
    
    security/keys/big_key.o: In function `big_key_crypt':
    big_key.c:(.text+0x29f): undefined reference to `crypto_aead_setkey'
    security/keys/big_key.o: In function `big_key_init':
    big_key.c:(.init.text+0x1a): undefined reference to `crypto_alloc_aead'
    big_key.c:(.init.text+0x45): undefined reference to `crypto_aead_setauthsize'
    big_key.c:(.init.text+0x77): undefined reference to `crypto_destroy_tfm'
    crypto/gcm.o: In function `gcm_hash_crypt_remain_continue':
    gcm.c:(.text+0x167): undefined reference to `crypto_ahash_finup'
    crypto/gcm.o: In function `crypto_gcm_exit_tfm':
    gcm.c:(.text+0x847): undefined reference to `crypto_destroy_tfm'
    
    When we 'select CRYPTO' like the other users, we always get a
    configuration that builds.
    
    Fixes: 428490e3 ("security/keys: rewrite all of big_key crypto")
    Signed-off-by: NArnd Bergmann <arnd@arndb.de>
    Signed-off-by: NDavid Howells <dhowells@redhat.com>
    3cd18d19
Kconfig 3.3 KB