From: Dragan Simic <dsimic@manjaro.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
olivia@selenic.com, didi.debian@cknow.org, heiko@sntech.de
Subject: Re: [PATCH 3/3] hwrng: Don't default to HW_RANDOM when UML_RANDOM is the trigger
Date: Sun, 09 Feb 2025 11:13:38 +0100 [thread overview]
Message-ID: <d6fd6707808ec4429071e5473c9c2dca@manjaro.org> (raw)
In-Reply-To: <Z6h7RoBpKd1ZDKhz@gondor.apana.org.au>
On 2025-02-09 10:54, Herbert Xu wrote:
> On Sun, Feb 09, 2025 at 10:37:52AM +0100, Dragan Simic wrote:
>>
>> Could you, please, clarify why we need(ed) the defaults at all?
>> Also, I'm a bit puzzled about what would be the defaults that are
>> actually needed? Are you actually referring to what I proposed
>> in my earlier response? [1] I'd appreciate a clarification.
>
> In general there shouldn't be any default. The only exception
> would be perhaps for embedded boards where the RNG is always
> present given the dependencies. But in that case the default
> should be conditional on the dependency (or perhaps the whole
> config should become unconditional).
>
> The current defaults are mostly there for historical reasons.
Thanks for the clarification.
I think it would be the best to get rid of the current defaults
in the drivers/char/hw_random/Kconfig file entirely, together with
updating as many of the affected arch/*/configs/*_defconfig files
as possible to select the relevant HW_RANDOM_* config option(s)
whenever that's a sane thing to do.
Such an approach should be both proper and least disruptive.
next prev parent reply other threads:[~2025-02-09 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 13:06 [PATCH 0/3] No longer " Dragan Simic
2025-01-15 13:07 ` [PATCH 1/3] hwrng: Use tabs as leading whitespace consistently in Kconfig Dragan Simic
2025-01-15 13:07 ` [PATCH 2/3] hwrng: Move one "tristate" Kconfig description to the usual place Dragan Simic
2025-01-15 13:07 ` [PATCH 3/3] hwrng: Don't default to HW_RANDOM when UML_RANDOM is the trigger Dragan Simic
2025-01-15 14:59 ` Diederik de Haas
2025-01-15 17:21 ` Dragan Simic
2025-02-09 9:15 ` Herbert Xu
2025-02-09 9:37 ` Dragan Simic
2025-02-09 9:54 ` Herbert Xu
2025-02-09 10:13 ` Dragan Simic [this message]
2025-02-09 10:22 ` [PATCH 0/3] No longer " Herbert Xu
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=d6fd6707808ec4429071e5473c9c2dca@manjaro.org \
--to=dsimic@manjaro.org \
--cc=didi.debian@cknow.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olivia@selenic.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®