From: "Stephan Müller" <smueller@chronox.de>
To: Palmer Dabbelt <palmerdabbelt@google.com>,
Christoph Hellwig <hch@infradead.org>
Cc: linux-riscv@lists.infradead.org, kernel-team@android.com,
kernel test robot <lkp@intel.com>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] crypto: jitterentropy - bind statically into kernel
Date: Sun, 04 Oct 2020 20:48:06 +0200 [thread overview]
Message-ID: <5692716.lOV4Wx5bFT@positron.chronox.de> (raw)
In-Reply-To: <20201002064905.GA27115@infradead.org>
The RISC-V architecture is about to implement the callback
random_get_entropy with a function that is not exported to modules.
Thus, the Jitter RNG is changed to be only bound statically into the
kernel removing the option to compile it as module.
Reported-by: Christoph Hellwig <hch@infradead.org>
Signed-off-by: Stephan Mueller <smueller@chronox.de>
---
crypto/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 094ef56ab7b4..5b20087b117f 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -1853,7 +1853,7 @@ config CRYPTO_DRBG
endif # if CRYPTO_DRBG_MENU
config CRYPTO_JITTERENTROPY
- tristate "Jitterentropy Non-Deterministic Random Number Generator"
+ bool "Jitterentropy Non-Deterministic Random Number Generator"
select CRYPTO_RNG
help
The Jitterentropy RNG is a noise that is intended
--
2.26.2
next prev parent reply other threads:[~2020-10-04 18:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200930065617.934638-1-palmerdabbelt@google.com>
2020-10-02 6:49 ` get_cycles from modular code in jitterentropy, was Re: [PATCH] clocksource: clint: Export clint_time_val for modules Christoph Hellwig
2020-10-02 6:55 ` Stephan Mueller
2020-10-04 18:48 ` Stephan Müller [this message]
2020-10-04 21:16 ` [PATCH] crypto: jitterentropy - bind statically into kernel Ard Biesheuvel
2020-10-04 22:05 ` Palmer Dabbelt
2020-10-05 6:19 ` Christoph Hellwig
2020-10-05 6:24 ` Ard Biesheuvel
2020-10-05 6:40 ` Stephan Mueller
2020-10-05 6:44 ` Christoph Hellwig
2020-10-05 6:44 ` Ard Biesheuvel
2020-10-05 6:56 ` Christoph Hellwig
2020-10-05 7:45 ` 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=5692716.lOV4Wx5bFT@positron.chronox.de \
--to=smueller@chronox.de \
--cc=hch@infradead.org \
--cc=kernel-team@android.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=palmerdabbelt@google.com \
/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