From: Randy Dunlap <rdunlap@xenotime•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Mimi Zohar <zohar@us•ibm.com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
linux-kbuild@vger•kernel.org
Subject: Re: linux-next: Tree for Aug 22 (evm)
Date: Mon, 22 Aug 2011 12:53:55 -0700 [thread overview]
Message-ID: <20110822125355.bb01d76b.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110822145304.980529cb921e5f1321c622da@canb.auug.org.au>
On Mon, 22 Aug 2011 14:53:04 +1000 Stephen Rothwell wrote:
> Hi all,
>
> [The kernel.org mirroring is a bit low today]
(on x86_64:)
When CONFIG_EVM=y, CONFIG_CRYPTO_HASH2=m, CONFIG_TRUSTED_KEYS=m,
CONFIG_ENCRYPTED_KEYS=m, the build fails with:
(.text+0x378aa): undefined reference to `key_type_encrypted'
evm_crypto.c:(.text+0x37992): undefined reference to `crypto_alloc_shash'
evm_crypto.c:(.text+0x37a24): undefined reference to `crypto_shash_setkey'
evm_crypto.c:(.text+0x37ad9): undefined reference to `crypto_shash_update'
evm_crypto.c:(.text+0x37aeb): undefined reference to `crypto_shash_final'
(.text+0x37b4b): undefined reference to `crypto_shash_update'
(.text+0x37c61): undefined reference to `crypto_shash_update'
(.text+0x37cb9): undefined reference to `crypto_shash_update'
even though EVM (Kconfig) selects ENCRYPTED_KEYS and TRUSTED_KEYS..
and even after I add "select CRYPTO_HASH2".
Is this because EVM is bool and kconfig is confused about 'select's
when a bool is selecting tristates? Shouldn't the tristates become
'y' instead of 'm' if they are selected by a bool that is 'y'?
xconfig shows these symbol values:
Symbol: EVM [=y]
Type : boolean
Prompt: EVM support
Defined at security/integrity/evm/Kconfig:1
Depends on: SECURITY [=y] && KEYS [=y] && TCG_TPM [=m]
Location:
-> Security options
Selects: CRYPTO_HMAC [=m] && CRYPTO_MD5 [=m] && CRYPTO_SHA1 [=m] && CRYPTO_HASH2 [=m] && ENCRYPTED_KEYS [=m] && TRUSTED_KEYS [=m]
Hm, changing TCG_TPM to =y also changes TRUSTED_KEYS and ENCRYPTED_KEYS and
lots of CRYPTO_ symbols from =m to =y. There must be some kind of min/max
symbol checking that is confused?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-08-22 19:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 4:53 linux-next: Tree for Aug 22 Stephen Rothwell
2011-08-22 16:10 ` linux-next: Tree for Aug 22 (drivers/power/pda_power.c) Randy Dunlap
2011-08-22 18:13 ` [PATCH -next] staging: fix comedi build when COMEDI_PCI is not enabled Randy Dunlap
2011-08-23 18:58 ` Greg KH
2011-08-23 20:03 ` Randy Dunlap
2011-08-22 18:30 ` [PATCH -next] power_supply: fix sysfs format warning Randy Dunlap
2011-08-23 13:27 ` Anton Vorontsov
2011-08-22 19:53 ` Randy Dunlap [this message]
2011-08-22 20:18 ` linux-next: Tree for Aug 22 (evm) Arnaud Lacombe
2011-08-23 0:47 ` Arnaud Lacombe
2011-08-23 0:49 ` Randy Dunlap
2011-08-23 2:09 ` Mimi Zohar
2011-08-23 2:24 ` Arnaud Lacombe
2011-08-24 2:07 ` Mimi Zohar
2011-08-23 2:32 ` Arnaud Lacombe
2011-08-23 23:40 ` Randy Dunlap
2011-08-24 2:10 ` Arnaud Lacombe
2011-08-26 12:39 ` Mimi Zohar
2011-08-26 17:00 ` Randy Dunlap
2011-08-27 6:06 ` Arnaud Lacombe
2011-09-02 0:32 ` Arnaud Lacombe
2011-09-02 1:40 ` Mimi Zohar
2011-09-02 2:21 ` Arnaud Lacombe
2011-09-02 15:01 ` Randy Dunlap
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=20110822125355.bb01d76b.rdunlap@xenotime.net \
--to=rdunlap@xenotime$(echo .)net \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=zohar@us$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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