From: Greg KH <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: stable@vger.kernel.org,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH stable 5.18 5.15 5.10 5.4] powerpc/pseries: wire up rng during setup_arch()
Date: Mon, 27 Jun 2022 13:02:05 +0200 [thread overview]
Message-ID: <YrmOLfbRIJuTnaOV@kroah.com> (raw)
In-Reply-To: <20220627100158.526135-1-Jason@zx2c4.com>
On Mon, Jun 27, 2022 at 12:01:58PM +0200, Jason A. Donenfeld wrote:
> commit e561e472a3d441753bd012333b057f48fef1045b upstream.
>
> The platform's RNG must be available before random_init() in order to be
> useful for initial seeding, which in turn means that it needs to be
> called from setup_arch(), rather than from an init call. Fortunately,
> each platform already has a setup_arch function pointer, which means
> it's easy to wire this up. This commit also removes some noisy log
> messages that don't add much.
>
> Fixes: a489043f4626 ("powerpc/pseries: Implement arch_get_random_long() based on H_RANDOM")
> Cc: stable@vger.kernel.org # v3.13+
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> Link: https://lore.kernel.org/r/20220611151015.548325-4-Jason@zx2c4.com
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> ---
> arch/powerpc/platforms/pseries/pseries.h | 2 ++
> arch/powerpc/platforms/pseries/rng.c | 11 +++--------
> arch/powerpc/platforms/pseries/setup.c | 2 ++
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-06-27 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 9:43 FAILED: patch "[PATCH] powerpc/pseries: wire up rng during setup_arch()" failed to apply to 5.18-stable tree gregkh
2022-06-27 10:01 ` [PATCH stable 5.18 5.15 5.10 5.4] powerpc/pseries: wire up rng during setup_arch() Jason A. Donenfeld
2022-06-27 11:02 ` Greg KH [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=YrmOLfbRIJuTnaOV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=christophe.leroy@csgroup.eu \
--cc=mpe@ellerman.id.au \
--cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).