From: "Ard Biesheuvel" <ardb@kernel.org>
To: "Eric Biggers" <ebiggers@kernel.org>, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David Howells" <dhowells@redhat.com>,
"Stephan Mueller" <smueller@chronox.de>
Subject: Re: [PATCH v7] crypto: jitterentropy - Use SHA-3 library
Date: Thu, 26 Feb 2026 15:05:50 +0100 [thread overview]
Message-ID: <d74eb790-83b7-42ef-bcbd-3a3c03ff1a51@app.fastmail.com> (raw)
In-Reply-To: <20260226010005.43528-1-ebiggers@kernel.org>
On Thu, 26 Feb 2026, at 02:00, Eric Biggers wrote:
> From: David Howells <dhowells@redhat.com>
>
> Make the jitterentropy RNG use the SHA-3 library API instead of
> crypto_shash. This ends up being quite a bit simpler, as various
> dynamic allocations and error checks become unnecessary.
>
> Signed-off-by: David Howells <dhowells@redhat.com>
> Co-developed-by: Eric Biggers <ebiggers@kernel.org>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
>
> This is a cleaned-up and rebased version of
> https://lore.kernel.org/linux-crypto/20251017144311.817771-7-dhowells@redhat.com/
> If there are no objections, I'll take this via libcrypto-next.
>
> crypto/Kconfig | 2 +-
> crypto/jitterentropy-kcapi.c | 114 +++++++++--------------------------
> crypto/jitterentropy.c | 25 ++++----
> crypto/jitterentropy.h | 19 +++---
> 4 files changed, 52 insertions(+), 108 deletions(-)
>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
next prev parent reply other threads:[~2026-02-26 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 1:00 Eric Biggers
2026-02-26 14:05 ` Ard Biesheuvel [this message]
2026-03-03 4:58 ` Eric Biggers
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=d74eb790-83b7-42ef-bcbd-3a3c03ff1a51@app.fastmail.com \
--to=ardb@kernel.org \
--cc=Jason@zx2c4.com \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
/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
all inboxes | Powered by JetHome®