From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 928] New: cryptoloop has unresolved symbols (includes fix)
Date: Tue, 15 Jul 2003 08:20:14 -0700 [thread overview]
Message-ID: <239370000.1058282414@[10.10.2.4]> (raw)
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
reply other threads:[~2003-07-15 15:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='239370000.1058282414@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).