From: Stephan Mueller <smueller@chronox.de>
To: herbert@gondor.apana.org.au
Cc: linux-crypto@vger.kernel.org
Subject: CTR mode: Kconfig cyclic dependency
Date: Thu, 09 Jun 2016 11:07:06 +0200 [thread overview]
Message-ID: <1465466750.NsZ2X8r4WP@positron.chronox.de> (raw)
Hi Herbert,
during the finalization of my patch set for converting the CTR DRBG over to
CTR AES, I ran into a Kconfig problem. Maybe you have an idea how to resolve
it.
As the CTR DRBG now uses the CTR mode, I added "select CRYPTO_CTR" to
CRYPTO_DRBG_CTR. This now lead to the following cyclic dependency:
crypto/Kconfig:1547:error: recursive dependency detected!
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
crypto/Kconfig:1547: symbol CRYPTO_DRBG_MENU is selected by
CRYPTO_RNG_DEFAULT
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
crypto/Kconfig:83: symbol CRYPTO_RNG_DEFAULT is selected by CRYPTO_SEQIV
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
crypto/Kconfig:255: symbol CRYPTO_SEQIV is selected by CRYPTO_CTR
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
crypto/Kconfig:286: symbol CRYPTO_CTR is selected by CRYPTO_DRBG_CTR
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"
crypto/Kconfig:1566: symbol CRYPTO_DRBG_CTR depends on CRYPTO_DRBG_MENU
i.e. CRYPTO_RNG_DEFAULT -> CRYPTO_DRBG_MENU -> CRYPTO_CTR -> CRYPTO_SEQIV ->
CRYPTO_RNG_DEFAULT
Thanks
Stephan
next reply other threads:[~2016-06-09 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 9:07 Stephan Mueller [this message]
2016-06-12 10:58 ` CTR mode: Kconfig cyclic dependency Herbert Xu
2016-06-12 11:05 ` Stephan Mueller
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=1465466750.NsZ2X8r4WP@positron.chronox.de \
--to=smueller@chronox.de \
--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