From: "Stephan Müller" <smueller@chronox.de>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Fwd: [linux-next:master 7274/8070] undefined reference to `crypto_alloc_shash'
Date: Sun, 09 Apr 2017 22:09:54 +0200 [thread overview]
Message-ID: <1827882.yksAJm9a6v@positron.chronox.de> (raw)
Hi Herbert,
I got the attached error report. This is due to CRYPTO_HASH2 is selected as m
whereas security/keys/dh.c is compiled as y. Note CRYPTO_HASH is selected as
y.
dh.c requires shash.
Kconfig for dh.c contains:
config KEY_DH_OPERATIONS
bool "Diffie-Hellman operations on retained keys"
depends on KEYS
select MPILIB
select CRYPTO_HASH
Shall I select CRYPTO_HASH2 instead or in addition to CRYPTO_HASH?
Thanks.
Ciao
Stephan
---------- Weitergeleitete Nachricht ----------
Betreff: [linux-next:master 7274/8070] undefined reference to
`crypto_alloc_shash'
Datum: Donnerstag, 6. April 2017, 10:03:30 CEST
Von: kbuild test robot <fengguang.wu@intel.com>
An: Stephan Mueller <smueller@chronox.de>
Kopie: kbuild-all@01.org, David Howells <dhowells@redhat.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
master
head: d203084e692ac2f656cf8c50449f8f90ca7875de
commit: f1c316a3ab9d24df6022682422fe897492f2c0c8 [7274/8070] KEYS: add
SP800-56A KDF support for DH
config: x86_64-randconfig-s0-04061437 (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout f1c316a3ab9d24df6022682422fe897492f2c0c8
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
security/built-in.o: In function `__keyctl_dh_compute':
>> (.text+0xa4f7): undefined reference to `crypto_alloc_shash'
security/built-in.o: In function `__keyctl_dh_compute':
>> (.text+0xa7b5): undefined reference to `crypto_shash_update'
security/built-in.o: In function `__keyctl_dh_compute':
(.text+0xa7ed): undefined reference to `crypto_shash_update'
security/built-in.o: In function `__keyctl_dh_compute':
>> (.text+0xa832): undefined reference to `crypto_shash_final'
security/built-in.o: In function `__keyctl_dh_compute':
(.text+0xa881): undefined reference to `crypto_shash_final'
security/built-in.o: In function `__keyctl_dh_compute':
>> (.text+0xa9bd): undefined reference to `crypto_destroy_tfm'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
-------------------------------------------------------------
next reply other threads:[~2017-04-09 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-09 20:09 Stephan Müller [this message]
2017-04-10 10:22 ` Fwd: [linux-next:master 7274/8070] undefined reference to `crypto_alloc_shash' Herbert Xu
2017-04-10 10:46 ` Stephan Müller
2017-04-11 10:50 ` Herbert Xu
2017-04-11 10:56 ` Stephan Müller
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=1827882.yksAJm9a6v@positron.chronox.de \
--to=smueller@chronox.de \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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