[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200329082909.193910-1-alexander.sverdlin@gmail.com>
Date: Sun, 29 Mar 2020 10:29:09 +0200
From: Alexander Sverdlin <alexander.sverdlin@...il.com>
To: Theodore Ts'o <tytso@....edu>, linux-kernel@...r.kernel.org
Cc: Alexander Sverdlin <alexander.sverdlin@...il.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Herbert Xu <herbert@...dor.apana.org.au>
Subject: [PATCH] random: Drop ARCH limitations for CONFIG_RANDOM_TRUST_CPU
The option itself looks attractive for the embedded devices which often
have HWRNG but less entropy from user-input. And these devices are often
ARM/ARM64 or MIPS. The reason to limit it to X86/S390/PPC is not obvious.
Signed-off-by: Alexander Sverdlin <alexander.sverdlin@...il.com>
---
drivers/char/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
index 26956c006987..abc874722251 100644
--- a/drivers/char/Kconfig
+++ b/drivers/char/Kconfig
@@ -539,7 +539,6 @@ endmenu
config RANDOM_TRUST_CPU
bool "Trust the CPU manufacturer to initialize Linux's CRNG"
- depends on X86 || S390 || PPC
default n
help
Assume that CPU manufacturer (e.g., Intel or AMD for RDSEED or
--
2.25.1
Powered by blists - more mailing lists