KernelCI discussions
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
	regressions@lists.linux.dev, laura.nao@collabora.com,
	shreeya.patel@collabora.com, broonie@kernel.org,
	kernelci-results@groups.io, kernelci@lists.linux.dev,
	Ard Biesheuvel <ardb@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...
Date: Tue, 18 Aug 2026 10:52:09 -0700	[thread overview]
Message-ID: <20260818175209.GA1675024@ax162> (raw)
In-Reply-To: <20260818165116.GA1335107@ax162>

On Tue, Aug 18, 2026 at 09:51:21AM -0700, Nathan Chancellor wrote:
> On Tue, Aug 18, 2026 at 09:19:04AM -0700, Nick Desaulniers wrote:
> > + Ard
> > 
> > On Mon, Aug 17, 2026 at 11:00 PM Thorsten Leemhuis
> > <regressions@leemhuis.info> wrote:
> > > Nathan, Nick, do you still care about clang problems like this?
> > 
> > Yes, from the logs, it looks like ARCH=arm allmodconfig with clang-21
> > (perhaps, there's a funny warning about the compiler version in the
> > logs).
> > 
> > > And do
> > > you by chance know what's wrong here?
> > >
> > > """
> > > <instantiation>:2:11: error: out of range pc-relative fixup value
> > >  ldr r10, =__per_cpu_offset
> > >           ^
> > > <instantiation>:2:11: error: out of range pc-relative fixup value
> > >  ldr tsk, =__current
> > >           ^
> > > <instantiation>:2:11: error: out of range pc-relative fixup value
> > >  ldr tsk, =__current
> > >           ^
> > 
> > Smells like the same problem that was addressed by
> > commit 5fe41793bc78 ("ARM: 9176/1: avoid literal references in inline assembly")
> > 
> > What tree was being tested? 5fe41793bc78 landed in v5.18-rc1. Whatever
> > was being tested is probably missing that patch.
> 
> As Mark notes, this is mainline. This error is visible with LLVM 23 as
> well. I bisected it to commit 79d27fd71854 ("arch: hookup fchroot()
> system call").
> 
> I do see that change in -next and there is no error there so was this a
> known issue that was fixed in another tree? I will keep looking.

It looks like commit 25900bd99d4d ("ARM: limit OABI support to StrongARM
CPUs") in the soc tree avoids this error by disabling CONFIG_OABI_COMPAT
for allmodconfig. If I disable that on top of allmodconfig with current
mainline, the error goes away.

I narrowed down a reproducer to

  $ cat arch/arm/configs/repro.config
  CONFIG_ARCH_MULTI_V6=y
  CONFIG_ARCH_REALVIEW=y
  CONFIG_COMPILE_TEST=y
  CONFIG_MACH_REALVIEW_PB1176=y
  CONFIG_OABI_COMPAT=y

  $ make -skj"$(nproc)" ARCH=arm LLVM=1 mrproper defconfig repro.config arch/arm/kernel/entry-common.o
  <instantiation>:2:11: error: out of range pc-relative fixup value
   ldr r10, =__per_cpu_offset
            ^
  <instantiation>:2:11: error: out of range pc-relative fixup value
   ldr tsk, =__current
            ^
  <instantiation>:2:11: error: out of range pc-relative fixup value
   ldr tsk, =__current
            ^

CONFIG_COMPILE_TEST is necessary because it turns off
CONFIG_ARM_HAS_GROUP_RELOCS, which seems relevant here.

-- 
Cheers,
Nathan

      reply	other threads:[~2026-08-18 17:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <178701474442.5156.12765087253678603047@kernelci.org>
2026-08-18  6:00 ` [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile Thorsten Leemhuis
2026-08-18 16:19   ` Nick Desaulniers
2026-08-18 16:28     ` Mark Brown
2026-08-18 16:51     ` Nathan Chancellor
2026-08-18 17:52       ` Nathan Chancellor [this message]

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=20260818175209.GA1675024@ax162 \
    --to=nathan@kernel.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=kernelci-results@groups.io \
    --cc=kernelci@lists.linux.dev \
    --cc=laura.nao@collabora.com \
    --cc=ndesaulniers@google.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=shreeya.patel@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox