mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Phil Elwell <phil@raspberrypi.com>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Stephen Boyd <swboyd@chromium.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Russell King <linux@armlinux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v2] random: defer crediting bootloader randomness to random_init()
Date: Tue, 7 Jun 2022 14:23:53 +0200	[thread overview]
Message-ID: <Yp9DWT3RttJGZhvu@zx2c4.com> (raw)
In-Reply-To: <a09c83a2-f3a3-6ae8-ca96-3560bd6b9f91@raspberrypi.com>

Hi Phil,

On Tue, Jun 07, 2022 at 01:19:41PM +0100, Phil Elwell wrote:
> After a trivial merge conflict (into 5.15) was resolved, this patch allows the 
> downstream kernel with CONFIG_RANDOM_TRUST_BOOTLOADER=y to boot cleanly. 
> However, it does delay the initialisation of crng significantly compared to my
> hack.
> 
> With v2:
> [    1.981493] bcm2835-rng 3f104000.rng: hwrng registered
> [   12.549190] random: crng init done

Thanks. It's because the patch is buggy :)

v3 coming right up.

Jason

  reply	other threads:[~2022-06-07 12:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 11:15 [PATCH] random: defer use of " Jason A. Donenfeld
2022-06-07 11:22 ` Jason A. Donenfeld
2022-06-07 11:32   ` [PATCH v2] random: defer crediting " Jason A. Donenfeld
2022-06-07 12:19     ` Phil Elwell
2022-06-07 12:23       ` Jason A. Donenfeld [this message]
2022-06-07 12:44         ` [PATCH v3] " Jason A. Donenfeld
2022-06-07 13:21           ` Phil Elwell
2022-06-07 13:51             ` Jason A. Donenfeld
2022-06-07 14:13               ` Phil Elwell
2022-06-07 11:55 ` [PATCH] random: defer use of " Ard Biesheuvel
2022-06-07 12:04   ` Jason A. Donenfeld
2022-06-07 12:15     ` Ard Biesheuvel
2022-06-07 12:21       ` Jason A. Donenfeld
2022-06-07 14:19         ` Ard Biesheuvel
2022-06-07 14:48           ` Jason A. Donenfeld
2022-06-07 14:51             ` Ard Biesheuvel

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=Yp9DWT3RttJGZhvu@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=phil@raspberrypi.com \
    --cc=swboyd@chromium.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
all inboxes | Powered by JetHome®