From: Michael Ellerman <mpe@ellerman.id.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>, Borislav Petkov <bp@suse.de>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: [PATCH v5] random: remove CONFIG_ARCH_RANDOM
Date: Mon, 18 Jul 2022 22:53:38 +1000 [thread overview]
Message-ID: <877d4aeg4t.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220708004032.733426-1-Jason@zx2c4.com>
"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> When RDRAND was introduced, there was much discussion on whether it
> should be trusted and how the kernel should handle that. Initially, two
> mechanisms cropped up, CONFIG_ARCH_RANDOM, a compile time switch, and
> "nordrand", a boot-time switch.
...
>
> arch/arm/include/asm/archrandom.h | 2 ++
> arch/arm64/Kconfig | 8 ------
> arch/arm64/include/asm/archrandom.h | 10 --------
> arch/arm64/kernel/cpufeature.c | 2 --
> arch/powerpc/Kconfig | 3 ---
> arch/powerpc/include/asm/archrandom.h | 3 ---
> arch/powerpc/include/asm/machdep.h | 2 --
> arch/powerpc/platforms/microwatt/Kconfig | 1 -
> arch/powerpc/platforms/powernv/Kconfig | 1 -
> arch/powerpc/platforms/pseries/Kconfig | 1 -
Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>, Borislav Petkov <bp@suse.de>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: Re: [PATCH v5] random: remove CONFIG_ARCH_RANDOM
Date: Mon, 18 Jul 2022 22:53:38 +1000 [thread overview]
Message-ID: <877d4aeg4t.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220708004032.733426-1-Jason@zx2c4.com>
"Jason A. Donenfeld" <Jason@zx2c4.com> writes:
> When RDRAND was introduced, there was much discussion on whether it
> should be trusted and how the kernel should handle that. Initially, two
> mechanisms cropped up, CONFIG_ARCH_RANDOM, a compile time switch, and
> "nordrand", a boot-time switch.
...
>
> arch/arm/include/asm/archrandom.h | 2 ++
> arch/arm64/Kconfig | 8 ------
> arch/arm64/include/asm/archrandom.h | 10 --------
> arch/arm64/kernel/cpufeature.c | 2 --
> arch/powerpc/Kconfig | 3 ---
> arch/powerpc/include/asm/archrandom.h | 3 ---
> arch/powerpc/include/asm/machdep.h | 2 --
> arch/powerpc/platforms/microwatt/Kconfig | 1 -
> arch/powerpc/platforms/powernv/Kconfig | 1 -
> arch/powerpc/platforms/pseries/Kconfig | 1 -
Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
cheers
_______________________________________________
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:[~2022-07-18 12:53 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 19:01 [PATCH] random: remove CONFIG_ARCH_RANDOM and "nordrand" Jason A. Donenfeld
2022-07-05 19:01 ` Jason A. Donenfeld
2022-07-05 19:01 ` Jason A. Donenfeld
2022-07-05 19:36 ` Borislav Petkov
2022-07-05 19:36 ` Borislav Petkov
2022-07-05 19:36 ` Borislav Petkov
2022-07-05 19:44 ` Jason A. Donenfeld
2022-07-05 19:44 ` Jason A. Donenfeld
2022-07-05 19:44 ` Jason A. Donenfeld
2022-07-05 19:57 ` Borislav Petkov
2022-07-05 19:57 ` Borislav Petkov
2022-07-05 19:57 ` Borislav Petkov
2022-07-05 21:50 ` H. Peter Anvin
2022-07-05 21:50 ` H. Peter Anvin
2022-07-05 21:50 ` H. Peter Anvin
2022-07-05 22:00 ` Borislav Petkov
2022-07-05 22:00 ` Borislav Petkov
2022-07-05 22:00 ` Borislav Petkov
2022-07-05 23:11 ` H. Peter Anvin
2022-07-05 23:11 ` H. Peter Anvin
2022-07-05 23:11 ` H. Peter Anvin
2022-07-06 12:23 ` Borislav Petkov
2022-07-06 12:23 ` Borislav Petkov
2022-07-06 12:23 ` Borislav Petkov
2022-07-06 16:42 ` H. Peter Anvin
2022-07-06 16:42 ` H. Peter Anvin
2022-07-06 16:42 ` H. Peter Anvin
2022-07-06 0:28 ` Jason A. Donenfeld
2022-07-06 0:28 ` Jason A. Donenfeld
2022-07-06 0:28 ` Jason A. Donenfeld
2022-07-06 0:32 ` [PATCH v2] random: remove CONFIG_ARCH_RANDOM Jason A. Donenfeld
2022-07-06 0:32 ` Jason A. Donenfeld
2022-07-06 6:41 ` Greg Kroah-Hartman
2022-07-06 6:41 ` Greg Kroah-Hartman
2022-07-06 6:41 ` Greg Kroah-Hartman
2022-07-06 8:40 ` Heiko Carstens
2022-07-06 8:40 ` Heiko Carstens
2022-07-06 8:40 ` Heiko Carstens
2022-07-06 10:54 ` [PATCH v3] " Jason A. Donenfeld
2022-07-06 10:54 ` Jason A. Donenfeld
2022-07-06 12:35 ` Borislav Petkov
2022-07-06 12:35 ` Borislav Petkov
2022-07-06 12:35 ` Borislav Petkov
2022-07-06 13:55 ` Jason A. Donenfeld
2022-07-06 13:55 ` Jason A. Donenfeld
2022-07-06 13:55 ` Jason A. Donenfeld
2022-07-06 14:35 ` [PATCH v4] " Jason A. Donenfeld
2022-07-06 14:35 ` Jason A. Donenfeld
2022-07-08 0:40 ` [PATCH v5] " Jason A. Donenfeld
2022-07-08 0:40 ` Jason A. Donenfeld
2022-07-13 15:46 ` Catalin Marinas
2022-07-13 15:46 ` Catalin Marinas
2022-07-13 15:46 ` Catalin Marinas
2022-07-18 12:53 ` Michael Ellerman [this message]
2022-07-18 12:53 ` Michael Ellerman
2022-08-12 13:50 ` Geert Uytterhoeven
2022-08-12 13:50 ` Geert Uytterhoeven
2022-08-12 13:50 ` Geert Uytterhoeven
2022-07-06 12:30 ` [PATCH] random: remove CONFIG_ARCH_RANDOM and "nordrand" Borislav Petkov
2022-07-06 12:30 ` Borislav Petkov
2022-07-06 12:30 ` Borislav Petkov
2022-07-06 14:55 ` Theodore Ts'o
2022-07-06 14:55 ` Theodore Ts'o
2022-07-06 14:55 ` Theodore Ts'o
2022-07-06 15:24 ` Jason A. Donenfeld
2022-07-06 15:24 ` Jason A. Donenfeld
2022-07-06 15:24 ` Jason A. Donenfeld
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=877d4aeg4t.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Jason@zx2c4.com \
--cc=agordeev@linux.ibm.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.