public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: linux-kbuild@vger.kernel.org
Cc: dhowells@redhat.com
Subject: Kconfig problem
Date: Mon, 07 Mar 2016 16:19:34 +0000	[thread overview]
Message-ID: <19064.1457367574@warthog.procyon.org.uk> (raw)

Hi,

I'm having some problems with Kconfig - the dependency resolver seems to be
getting things wrong.

I have an option:

	config SYSTEM_TRUSTED_KEYRING
		bool "Provide system-wide ring of trusted keys"
		depends on KEYS
		depends on ASYMMETRIC_KEY_TYPE

which, as can be seen, depends on:

	menuconfig ASYMMETRIC_KEY_TYPE
		tristate "Asymmetric (public-key cryptographic) key type"
		depends on KEYS

But I can set CONFIG_SYSTEM_TRUSTED_KEYRING=y and CONFIG_ASYMMETRIC_KEY_TYPE=m
and the Kconfig processor is quite happy - but, of course, the kernel doesn't
link.

Yes, I could set ASYMMETRIC_KEY_TYPE to be a bool, but if
SYSTEM_TRUSTED_KEYRING is not set, there's no reason it couldn't be a module.

If I change the first option to:

	config SYSTEM_TRUSTED_KEYRING
		bool "Provide system-wide ring of trusted keys"
		select KEYS
		select ASYMMETRIC_KEY_TYPE

then it complains that there's a dependency loop.

	scripts/kconfig/conf  --silentoldconfig Kconfig
	crypto/Kconfig:15:error: recursive dependency detected!
	For a resolution refer to Documentation/kbuild/kconfig-language.txt
	subsection "Kconfig recursive dependency limitations"
	crypto/Kconfig:15:	symbol CRYPTO is selected by TRUSTED_KEYS
	For a resolution refer to Documentation/kbuild/kconfig-language.txt
	subsection "Kconfig recursive dependency limitations"
	security/keys/Kconfig:51:	symbol TRUSTED_KEYS depends on KEYS
	For a resolution refer to Documentation/kbuild/kconfig-language.txt
	subsection "Kconfig recursive dependency limitations"
	security/keys/Kconfig:5:	symbol KEYS is selected by SYSTEM_TRUSTED_KEYRING
	For a resolution refer to Documentation/kbuild/kconfig-language.txt
	subsection "Kconfig recursive dependency limitations"
	certs/Kconfig:17:	symbol SYSTEM_TRUSTED_KEYRING is selected by KEXEC_BZIMAGE_VERIFY_SIG
	For a resolution refer to Documentation/kbuild/kconfig-language.txt
	subsection "Kconfig recursive dependency limitations"
	arch/x86/Kconfig:1815:	symbol KEXEC_BZIMAGE_VERIFY_SIG depends on KEXEC_VERIFY_SIG
	For a resolution refer to Documentation/kbuild/kconfig-language.txt
	subsection "Kconfig recursive dependency limitations"
	arch/x86/Kconfig:1804:	symbol KEXEC_VERIFY_SIG depends on KEXEC_FILE
	For a resolution refer to Documentation/kbuild/kconfig-language.txt
	subsection "Kconfig recursive dependency limitations"
	arch/x86/Kconfig:1791:	symbol KEXEC_FILE depends on CRYPTO
	warning: (EXT4_ENCRYPTION && F2FS_FS_ENCRYPTION && EVM) selects ENCRYPTED_KEYS which has unmet direct dependencies (KEYS)
	warning: (MAC802154 && EXT4_ENCRYPTION && F2FS_FS_ENCRYPTION) selects CRYPTO_CTR which has unmet direct dependencies (CRYPTO)
	warning: (MODULE_SIG_SHA224 && MODULE_SIG_SHA256 && BT && LUSTRE_FS && EXT4_ENCRYPTION && F2FS_FS_ENCRYPTION && CIFS && ENCRYPTED_KEYS) selects CRYPTO_SHA256 which has unmet direct dependencies (CRYPTO)


If there's a dependency loop with select here, then there must be a dependency
loop with depends on here too, since A selects B is a dependency of A on B,
just as is A depends on B.

Any thoughts on how to resolve this?

David

             reply	other threads:[~2016-03-07 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 16:19 David Howells [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-10 12:58 Kconfig problem Andreas Ziegler

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=19064.1457367574@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-kbuild@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