[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBUHlGvZuI2O0bbs@arm.com>
Date: Fri, 2 May 2025 18:57:40 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Yeoreum Yun <yeoreum.yun@....com>, will@...nel.org, nathan@...nel.org,
nick.desaulniers+lkml@...il.com, morbo@...gle.com,
justinstitt@...gle.com, broonie@...nel.org, maz@...nel.org,
oliver.upton@...ux.dev, frederic@...nel.org, joey.gouly@....com,
james.morse@....com, hardevsinh.palaniya@...iconsignals.io,
shameerali.kolothum.thodi@...wei.com, ryan.roberts@....com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, stable@...r.kernel.org
Subject: Re: [PATCH] arm64/cpufeature: annotate arm64_use_ng_mappings with
ro_after_init to prevent wrong idmap generation
On Fri, May 02, 2025 at 06:41:33PM +0200, Ard Biesheuvel wrote:
> Making arm64_use_ng_mappings __ro_after_init seems like a useful
> change by itself, so I am not objecting to that. But we don't solve it
> more fundamentally, please at least add a big fat comment why it is
> important that the variable remains there.
Maybe something like the section reference checker we use for __init -
verify that the early C code does not refer anything in the BSS section.
--
Catalin
Powered by blists - more mailing lists