[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <174626735218.2189871.10298017577558632540.b4-ty@arm.com>
Date: Sat, 3 May 2025 11:16:12 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: 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,
joey.gouly@....com,
shameerali.kolothum.thodi@...wei.com,
james.morse@....com,
hardevsinh.palaniya@...iconsignals.io,
ardb@...nel.org,
ryan.roberts@....com,
Yeoreum Yun <yeoreum.yun@....com>
Cc: linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev,
stable@...r.kernel.org
Subject: Re: [PATCH v2] arm64/cpufeature: annotate arm64_use_ng_mappings with ro_after_init to prevent wrong idmap generation
On Fri, 02 May 2025 19:04:12 +0100, Yeoreum Yun wrote:
> create_init_idmap() could be called before .bss section initialization
> which is done in early_map_kernel().
> Therefore, data/test_prot could be set incorrectly by PTE_MAYBE_NG macro.
>
> PTE_MAYBE_NG macro set NG bit according to value of "arm64_use_ng_mappings".
> and this variable places in .bss section.
>
> [...]
Applied to arm64 (for-next/fixes), with some slight tweaking of the
comment, thanks!
[1/1] arm64/cpufeature: annotate arm64_use_ng_mappings with ro_after_init to prevent wrong idmap generation
https://git.kernel.org/arm64/c/12657bcd1835
--
Catalin
Powered by blists - more mailing lists