[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHmME9ocwrUZoi=AyTsaWoBLyy_FL_uVenZ+3N5wFHbOHR-vSg@mail.gmail.com>
Date: Thu, 2 Jun 2022 23:10:45 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Stephen Boyd <swboyd@...omium.org>, Will Deacon <will@...nel.org>,
Dominik Brodowski <linux@...inikbrodowski.net>,
Ard Biesheuvel <ardb@...nel.org>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
Douglas Anderson <dianders@...omium.org>,
Hsin-Yi Wang <hsinyi@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>, patches@...ts.linux.dev,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] arm64: Initialize jump labels before setup_machine_fdt()
+Greg
Hi Catalin,
On Thu, Jun 2, 2022 at 11:08 PM Catalin Marinas <catalin.marinas@....com> wrote:
>
> On Thu, Jun 02, 2022 at 10:18:04PM +0200, Jason A. Donenfeld wrote:
> > On Thu, Jun 2, 2022 at 9:46 PM Catalin Marinas <catalin.marinas@....com> wrote:
> > > On Thu, Jun 02, 2022 at 09:42:49PM +0200, Jason A. Donenfeld wrote:
> > > > On Thu, Jun 2, 2022 at 9:41 PM Catalin Marinas <catalin.marinas@....com> wrote:
> > > > > On Wed, 1 Jun 2022 19:21:09 -0700, Stephen Boyd wrote:
> > > > > > A static key warning splat appears during early boot on arm64 systems
> > > > > > that credit randomness from devicetrees that contain an "rng-seed"
> > > > > > property. This is because setup_machine_fdt() is called before
> > > > > > jump_label_init() during setup_arch(). Let's swap the order of these two
> > > > > > calls so that jump labels are initialized before the devicetree is
> > > > > > unflattened and the rng seed is credited.
> > > > > >
> > > > > > [...]
> > > > >
> > > > > Applied to arm64 (for-next/core), thanks!
> > > > >
> > > > > [1/1] arm64: Initialize jump labels before setup_machine_fdt()
> > > > > https://git.kernel.org/arm64/c/73e2d827a501
> > > >
> > > > I'm not sure precisely what your for-next tag corresponds to, but just
> > > > FYI, this should probably go into 5.19 asap and be marked for stable@.
> > >
> > > The for-next/core branch should go in 5.19-rc1 (I'll send a pull request
> > > tomorrow). There's no need to cc stable since the fixed commit just went
> > > in (unless you mean something else by "marked for stable").
> >
> > It is actually in stable, so please do CC. Otherwise I'll just forward manually.
>
> Ah, I didn't know this (the fixed commit doesn't have a cc stable
> either). So please forward it manually once Linus pulls it.
Will do.
Jason
Powered by blists - more mailing lists