[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250418120216.2968994-1-daniel@0x0f.com>
Date: Fri, 18 Apr 2025 21:02:16 +0900
From: Daniel Palmer <daniel@...f.com>
To: herbert@...dor.apana.org.au,
davem@...emloft.net,
Jason@...c4.com,
linux-crypto@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Daniel Palmer <daniel@...ngy.jp>
Subject: [PATCH] lib/crypto: blake2s: Disable self test if CONFIG_CRYPTO isn't enabled
From: Daniel Palmer <daniel@...ngy.jp>
Currently CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is used to remove
the self test code. CONFIG_CRYPTO_MANAGER_DISABLE_TESTS depends on
CONFIG_CRYPTO so its impossible to disable the self test without
enabling CONFIG_CRYPTO.
If you don't want CONFIG_CRYPTO you probably don't want self tests
so remove the self tests in that case too.
Fixes: 66d7fb94e4ff ("crypto: blake2s - generic C library implementation and selftest")
Signed-off-by: Daniel Palmer <daniel@...ngy.jp>
---
lib/crypto/blake2s.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/crypto/blake2s.c b/lib/crypto/blake2s.c
index 71a316552cc5..89d54e462fb5 100644
--- a/lib/crypto/blake2s.c
+++ b/lib/crypto/blake2s.c
@@ -60,7 +60,8 @@ EXPORT_SYMBOL(blake2s_final);
static int __init blake2s_mod_init(void)
{
- if (!IS_ENABLED(CONFIG_CRYPTO_MANAGER_DISABLE_TESTS) &&
+ if (IS_ENABLED(CONFIG_CRYPTO) &&
+ !IS_ENABLED(CONFIG_CRYPTO_MANAGER_DISABLE_TESTS) &&
WARN_ON(!blake2s_selftest()))
return -ENODEV;
return 0;
--
2.47.2
Powered by blists - more mailing lists