[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yp8xz0gfsRKgSO/n@zx2c4.com>
Date: Tue, 7 Jun 2022 13:09:03 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Phil Elwell <phil@...pberrypi.com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Russell King <rmk+kernel@...linux.org.uk>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
LKML <linux-kernel@...r.kernel.org>,
Catalin Marinas <catalin.marinas@....com>,
Stephen Boyd <swboyd@...omium.org>,
Ard Biesheuvel <ardb@...nel.org>,
stable <stable@...r.kernel.org>
Subject: Re: [PATCH v2] ARM: initialize jump labels before setup_machine_fdt()
Hi Phil,
On Tue, Jun 07, 2022 at 12:04:13PM +0100, Phil Elwell wrote:
> A clean 5.15.45 boots cleanly, whereas a downstream kernel shows the static key
> warning (but it does go on to boot). The significant difference is that our
> defconfigs set CONFIG_RANDOM_TRUST_BOOTLOADER=y - defining that on top of
> multi_v7_defconfig demonstrates the issue on a clean 5.15.45. Conversely, not
> setting that option in a downstream kernel build avoids the warning
Ah, that makes sense. Note that I've got a patch out for changing that
defconfig as well to be Y, which means the CI will catch this sort of
thing in the future.
Jason
Powered by blists - more mailing lists