All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: will@kernel.org, nathan@kernel.org,
	nick.desaulniers+lkml@gmail.com, morbo@google.com,
	justinstitt@google.com, broonie@kernel.org, maz@kernel.org,
	oliver.upton@linux.dev, joey.gouly@arm.com,
	shameerali.kolothum.thodi@huawei.com, james.morse@arm.com,
	hardevsinh.palaniya@siliconsignals.io, ardb@kernel.org,
	ryan.roberts@arm.com, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] arm64/cpufeature: annotate arm64_use_ng_mappings with ro_after_init to prevent wrong idmap generation
Date: Tue, 6 May 2025 10:09:27 +0100	[thread overview]
Message-ID: <aBnRx4do8Ly0llZ8@arm.com> (raw)
In-Reply-To: <aBnDqvY5c6a3qQ4H@e129823.arm.com>

On Tue, May 06, 2025 at 09:09:14AM +0100, Yeoreum Yun wrote:
> > On Sat, May 03, 2025 at 09:23:27PM +0100, Yeoreum Yun wrote:
> > > Hi Catalin,
> > >
> > > > On Sat, May 03, 2025 at 11:16:12AM +0100, Catalin Marinas wrote:
> > > > > 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
> > > >
> > > > I'm going to drop this for now. The kernel compiled with a clang 19.1.5
> > > > version I have around (Debian sid) fails to boot, gets stuck early on:
> > > >
> > > > $ clang --version
> > > > Debian clang version 19.1.5 (1)
> > > > Target: aarch64-unknown-linux-gnu
> > > > Thread model: posix
> > > > InstalledDir: /usr/lib/llvm-19/bin
> > > >
> > > > I didn't have time to investigate, disassemble etc. I'll have a look
> > > > next week.
> > >
> > > Just for your information.
> > > When I see the debian package, clang 19.1.5-1 doesn't supply anymore:
> > >  - https://ftp.debian.org/debian/pool/main/l/llvm-toolchain-19/
> > >
> > > and the default version for sid is below:
> > >
> > > $ clang-19 --version
> > > Debian clang version 19.1.7 (3)
> > > Target: aarch64-unknown-linux-gnu
> > > Thread model: posix
> > > InstalledDir: /usr/lib/llvm-19/bin
> > >
> > > When I tested with above version with arm64-linux's for-next/fixes
> > > including this patch. it works well.
> >
> > It doesn't seem to be toolchain related. It fails with gcc as well from
> > Debian stable but you'd need some older CPU (even if emulated, e.g.
> > qemu). It fails with Cortex-A72 (guest on Raspberry Pi 4) but not
> > Neoverse-N2. Also changing the annotation from __ro_after_init to
> > __read_mostly also works.
> 
> Thanks to let me know. But still I've failed to reproduce this
> on Cortex-a72 and any older cpu on qeum.
> If you don't mind, would you share your Kconfig?

Just defconfig with gcc (Debian 12.2.0-14) 12.2.0. It fails for me with
"qemu -bios /usr/share/qemu-efi-aarch64/QEMU_EFI.fd -cpu cortex-a53" (I
have qemu 9.1.1 around, I don't think that's relevant).

-- 
Catalin


  parent reply	other threads:[~2025-05-06 10:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-02 18:04 [PATCH v2] arm64/cpufeature: annotate arm64_use_ng_mappings with ro_after_init to prevent wrong idmap generation Yeoreum Yun
2025-05-03 10:16 ` Catalin Marinas
2025-05-03 14:11   ` Catalin Marinas
2025-05-03 20:23     ` Yeoreum Yun
2025-05-05 19:05       ` Catalin Marinas
2025-05-06  8:09         ` Yeoreum Yun
2025-05-06  8:15           ` Ryan Roberts
2025-05-06  8:53             ` Yeoreum Yun
2025-05-06 10:12               ` Catalin Marinas
2025-05-06 10:38                 ` Yeoreum Yun
2025-05-06 10:13               ` Ryan Roberts
2025-05-06  9:41             ` Ard Biesheuvel
2025-05-06 10:08               ` Ryan Roberts
2025-05-06 10:47                 ` Yeoreum Yun
2025-05-06 10:49                   ` Catalin Marinas
2025-05-06 10:57                     ` Yeoreum Yun
2025-05-06 10:17               ` Catalin Marinas
2025-05-06 10:22                 ` Ryan Roberts
2025-05-06 10:29                   ` Catalin Marinas
2025-05-06 10:36                   ` Yeoreum Yun
2025-05-06  9:09           ` Catalin Marinas [this message]
2025-05-06 10:49     ` Catalin Marinas

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=aBnRx4do8Ly0llZ8@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=hardevsinh.palaniya@siliconsignals.io \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=justinstitt@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=maz@kernel.org \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=oliver.upton@linux.dev \
    --cc=ryan.roberts@arm.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=stable@vger.kernel.org \
    --cc=will@kernel.org \
    --cc=yeoreum.yun@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.