Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 5 Apr 2021 15:50:16 -0700
From:   Eric Biggers <ebiggers@kernel.org>
To:     Julian Braha <julianbraha@gmail.com>
Cc:     herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
        linux-crypto@vger.kernel.org, fazilyildiran@gmail.com
Subject: Re: [PATCH] crypto: fix CRYPTO_LIB_* dependencies on CRYPTO
Message-ID: <YGuUKBPHRqjmjdQd@gmail.com>
References: <20210405150438.177783-1-julianbraha@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210405150438.177783-1-julianbraha@gmail.com>
Precedence: bulk

On Mon, Apr 05, 2021 at 11:04:38AM -0400, Julian Braha wrote:
> Currently, when a config option selects a
> CRYPTO_LIB_* option while CRYPTO is disabled,
> Kbuild gives an unmet dependency. However,
> these config options do not actually need to
> depend on CRYPTO.
> 
> Signed-off-by: Julian Braha <julianbraha@gmail.com>
> ---
>  crypto/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/crypto/Kconfig b/crypto/Kconfig
> index 5809cc198fa7..fb7eca5cb8c6 100644
> --- a/crypto/Kconfig
> +++ b/crypto/Kconfig
> @@ -1870,9 +1870,9 @@ config CRYPTO_STATS
>  config CRYPTO_HASH_INFO
>  	bool
>  
> -source "lib/crypto/Kconfig"
>  source "drivers/crypto/Kconfig"
>  source "crypto/asymmetric_keys/Kconfig"
>  source "certs/Kconfig"
>  
>  endif	# if CRYPTO
> +source "lib/crypto/Kconfig"
> -- 

Actually some of the files in lib/crypto/ do depend on CRYPTO.  For example,
there are calls to crypto_xor_cpy() and crypto_memneq(), which call functions
defined in crypto/algapi.c and crypto/memneq.c.  These helper functions would
need to be moved into lib/crypto/ for this to work.

- Eric