From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: suzuki.poulose@arm.com, Catalin Marinas <catalin.marinas@arm.com>,
ard.biesheuvel@linaro.org,
Richard Henderson <richard.henderson@linaro.org>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v8 3/3] arm64: Use v8.5-RNG entropy for KASLR seed
Date: Wed, 8 Jan 2020 17:21:59 +0000 [thread overview]
Message-ID: <20200108172159.GJ49203@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20200107183540.54794-4-broonie@kernel.org>
On Tue, Jan 07, 2020 at 06:35:40PM +0000, Mark Brown wrote:
> When seeding KALSR on a system where we have architecture level random
> number generation make use of that entropy, mixing it in with the seed
> passed by the bootloader. Since this is run very early in init before
> feature detection is complete we open code rather than use archrandom.h.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> arch/arm64/kernel/kaslr.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/kaslr.c b/arch/arm64/kernel/kaslr.c
> index 2a11a962e571..fc38c4c25eb6 100644
> --- a/arch/arm64/kernel/kaslr.c
> +++ b/arch/arm64/kernel/kaslr.c
> @@ -81,7 +81,8 @@ static __init const u8 *kaslr_get_cmdline(void *fdt)
> u64 __init kaslr_early_init(u64 dt_phys)
> {
> void *fdt;
> - u64 seed, offset, mask, module_range;
> + u64 seed, offset, mask, module_range, ftr;
> + unsigned long raw;
> const u8 *cmdline, *str;
> int size;
>
> @@ -120,6 +121,18 @@ u64 __init kaslr_early_init(u64 dt_phys)
> return 0;
> }
>
> + /*
> + * Mix in any entropy obtainable architecturally, open coded
> + * since this runs extremely early.
> + */
> + if (IS_ENABLED(CONFIG_ARCH_RANDOM)) {
> + ftr = read_sysreg_s(SYS_ID_AA64ISAR0_EL1);
> + if ((ftr >> ID_AA64ISAR0_RNDR_SHIFT) & 0xf) {
> + if (__arm64_rndr(&raw))
> + seed += raw;
> + }
> + }
This looks good. If we add the helper I suggest in patch 2, we can
reduce this down to:
/* Mix in any entropy obtainable architecturally */
if (__early_cpu_has_rndr()) {
unsigned long raw;
if (__arm64_rndr(&raw))
seed += raw;
}
... which keeps all the RNG bits in one place.
Thanks,
Mark.
> +
> if (!seed) {
> kaslr_status = KASLR_DISABLED_NO_SEED;
> return 0;
> --
> 2.20.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-08 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 18:35 [PATCH v8 0/3] ARMv8.5-RNG support Mark Brown
2020-01-07 18:35 ` [PATCH v8 1/3] arm64: Implement archrandom.h for ARMv8.5-RNG Mark Brown
2020-01-08 17:18 ` Mark Rutland
2020-01-07 18:35 ` [PATCH v8 2/3] arm64: random: Add data to pool from setup_arch() Mark Brown
2020-01-08 17:20 ` Mark Rutland
2020-01-08 17:36 ` Mark Brown
2020-01-07 18:35 ` [PATCH v8 3/3] arm64: Use v8.5-RNG entropy for KASLR seed Mark Brown
2020-01-08 17:21 ` Mark Rutland [this message]
2020-01-08 17:38 ` Ard Biesheuvel
2020-01-08 17:44 ` Mark Brown
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=20200108172159.GJ49203@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=richard.henderson@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/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