http://bugme.osdl.org/show_bug.cgi?id=928
Summary: cryptoloop has unresolved symbols (includes fix)
Kernel Version: 2.6.0-test1
Status: NEW
Severity: blocking
Owner: bugme-janitors@lists.osdl.org
Submitter: andy-kernel.388488@dustman.net
Distribution: Gentoo 1.4
Hardware Environment: Athlon-XP, Nvidia NForce2 chipset
Software Environment:
Problem Description:
WARNING: /lib/modules/2.6.0-test1/kernel/drivers/block/cryptoloop.ko needs
unknown symbol crypto_alloc_tfm
WARNING: /lib/modules/2.6.0-test1/kernel/drivers/block/cryptoloop.ko needs
unknown symbol crypto_free_tfm
Steps to reproduce:
CONFIG_BLK_DEV_CRYPTOLOOP=m
# CONFIG_CRYPTO is not set
Fix: Obviously CONFIG_CRYPTO should be set. This is due to an error in the
Kconfig. When the following patch is applied, the BLK_DEV_CRYPTOLOOP option will
not appear unless CRYPTO is set, which fixes the unresolved symbol problem
(works with both on or both off):
--- drivers/block/Kconfig.orig 2003-07-14 22:54:19.000000000 -0400
+++ drivers/block/Kconfig 2003-07-15 00:33:33.000000000 -0400
@@ -264,7 +264,7 @@
config BLK_DEV_CRYPTOLOOP
tristate "Cryptoloop Support"
- depends on BLK_DEV_LOOP
+ depends on BLK_DEV_LOOP && CRYPTO
---help---
Say Y here if you want to be able to use the ciphers that are
provided by the CryptoAPI as loop transformation. This might be
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 15 2003 - 22:00:58 EST