From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
quic_omprsing@quicinc.com, quic_bjorande@quicinc.com,
neil.armstrong@linaro.org, linux-arm-msm@vger.kernel.org,
olivia@selenic.com, ebiggers@kernel.org,
neeraj.soni@oss.qualcomm.com, dmitry.baryshkov@oss.qualcomm.com,
konrad.dybcio@oss.qualcomm.com
Subject: Re: [PATCH v2 0/4] qcom-rng fixes and cleanups
Date: Sun, 5 Jul 2026 16:26:55 +0800 [thread overview]
Message-ID: <akoVT0XHNhxy9-ej@gondor.apana.org.au> (raw)
In-Reply-To: <20260608175848.2045229-1-ebiggers@kernel.org>
Eric Biggers <ebiggers@kernel.org> wrote:
> This series fixes several bugs in qcom-rng, including failure to enable
> the clock before accessing the hardware, generating biased random
> numbers, and generating duplicate or non-random numbers due to missing
> locking. To fix the latter bug, it drops the support for the
> duplicative crypto_rng interface, which isn't used in practice, leaving
> just hwrng which is the one that actually matters.
>
> This series is targeting cryptodev/master
>
> Changed in v2:
> - Changed patch 3 to make the driver continue to be bound even when
> hwrng is unsupported.
> - Added blank line in patch 2
> - Added Reviewed-by
>
> Eric Biggers (4):
> crypto: qcom-rng - Enable clock in hwrng case
> crypto: qcom-rng - Allow zero as a random number
> crypto: qcom-rng - Remove crypto_rng interface
> hwrng: qcom - Move qcom-rng.c into drivers/char/hw_random/
>
> arch/arm/configs/multi_v7_defconfig | 2 +-
> arch/arm/configs/qcom_defconfig | 2 +-
> arch/arm64/configs/defconfig | 2 +-
> drivers/char/hw_random/Kconfig | 11 ++
> drivers/char/hw_random/Makefile | 1 +
> drivers/{crypto => char/hw_random}/qcom-rng.c | 156 +++---------------
> drivers/crypto/Kconfig | 12 --
> drivers/crypto/Makefile | 1 -
> drivers/gpu/drm/ci/arm64.config | 2 +-
> 9 files changed, 41 insertions(+), 148 deletions(-)
> rename drivers/{crypto => char/hw_random}/qcom-rng.c (53%)
>
>
> base-commit: 79bbe453e5bfa6e1c6aa2e8329bfc8f152b81c9b
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2026-07-05 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 17:58 Eric Biggers
2026-06-08 17:58 ` [PATCH v2 1/4] crypto: qcom-rng - Enable clock in hwrng case Eric Biggers
2026-06-08 17:58 ` [PATCH v2 2/4] crypto: qcom-rng - Allow zero as a random number Eric Biggers
2026-06-08 17:58 ` [PATCH v2 3/4] crypto: qcom-rng - Remove crypto_rng interface Eric Biggers
2026-06-08 18:31 ` Dmitry Baryshkov
2026-06-08 17:58 ` [PATCH v2 4/4] hwrng: qcom - Move qcom-rng.c into drivers/char/hw_random/ Eric Biggers
2026-07-05 8:26 ` Herbert Xu [this message]
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=akoVT0XHNhxy9-ej@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=ebiggers@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.soni@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=olivia@selenic.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_omprsing@quicinc.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
all inboxes | Powered by JetHome®