[REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[KernelCI bot]

New build issue found on mainline/master:

---
 in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile.build:435) [logspec:kbuild,kbuild.compiler]
---

Log excerpt:
=====================================================

=====================================================

When fixing this issue, please attribute this report according to the
patch submission rules:

Reported-by: kernelci.org bot <bot@kernelci.org>
Link: https://lore.kernel.org/all/178701474442.5156.12765087253678603047@kernelci.org/

For complete logs and details about the environment used, see the issue
on the KernelCI dashboard:

- dashboard: https://d.kernelci.org/i/maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03
- giturl: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
- commit HEAD:  ff68e5f557f69a08fdcfa4ce8b1b809d63bd4f45

# Builds where the incident occurred:

## defconfig+allmodconfig+CONFIG_FRAME_WARN=2048 on (arm):
- compiler: clang-21
- config: None
- dashboard: https://d.kernelci.org/build/maestro:6a838f2962f33761c0d6680b

#regzbot introduced: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f..ff68e5f557f69a08fdcfa4ce8b1b809d63bd4f45
#regzbot link: https://d.kernelci.org/i/maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03

#kernelci issue maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03

--
This is an experimental report format. Please send feedback in!
Talk to us at kernelci@lists.linux.dev

Made with love by the KernelCI team - https://kernelci.org

Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[Thorsten Leemhuis]

On 8/18/26 02:59, KernelCI bot wrote:
> New build issue found on mainline/master:
> 
> ---
>  in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile.build:435) [logspec:kbuild,kbuild.compiler]
> ---
> 
> Log excerpt:
> =====================================================

Missing for some reason. See below for one, grabbed it from
https://d.kernelci.org/log-viewer?itemId=maestro%3A6a838f2962f33761c0d6680b&type=build&url=https%3A%2F%2Ffiles.kernelci.org%2Fkbuild-clang-21-arm-allmodconfig-6a838f2962f33761c0d6680b%2Fbuild.log.gz

Nathan, Nick, do you still care about clang problems like this? 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
          ^
make[5]: *** [/tmp/kci/linux/scripts/Makefile.build:435:
arch/arm/kernel/entry-common.o] Error 1
make[5]: Target 'arch/arm/kernel/' not remade because of errors.
make[4]: *** [/tmp/kci/linux/scripts/Makefile.build:549:
arch/arm/kernel] Error 2
make[4]: Target 'arch/arm/' not remade because of errors.
make[3]: *** [/tmp/kci/linux/scripts/Makefile.build:549: arch/arm] Error 2
make[3]: Target './' not remade because of errors.
make[2]: *** [/tmp/kci/linux/Makefile:2187: .] Error 2
make[2]: Target '__all' not remade because of errors.
make[1]: *** [/tmp/kci/linux/Makefile:248: __sub-make] Error 2
make[1]: Target '__all' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2
make: Target '__all' not remade because of errors.
"""
Ciao, Thorsten


> =====================================================
> 
> When fixing this issue, please attribute this report according to the
> patch submission rules:
> 
> Reported-by: kernelci.org bot <bot@kernelci.org>
> Link: https://lore.kernel.org/all/178701474442.5156.12765087253678603047@kernelci.org/
> 
> For complete logs and details about the environment used, see the issue
> on the KernelCI dashboard:
> 
> - dashboard: https://d.kernelci.org/i/maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03
> - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> - commit HEAD:  ff68e5f557f69a08fdcfa4ce8b1b809d63bd4f45
> 
> # Builds where the incident occurred:
> 
> ## defconfig+allmodconfig+CONFIG_FRAME_WARN=2048 on (arm):
> - compiler: clang-21
> - config: None
> - dashboard: https://d.kernelci.org/build/maestro:6a838f2962f33761c0d6680b
> 
> #regzbot introduced: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f..ff68e5f557f69a08fdcfa4ce8b1b809d63bd4f45
> #regzbot link: https://d.kernelci.org/i/maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03
> 
> #kernelci issue maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03
> 
> --
> This is an experimental report format. Please send feedback in!
> Talk to us at kernelci@lists.linux.dev
> 
> Made with love by the KernelCI team - https://kernelci.org
> 

Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[Nick Desaulniers]

+ Ard

On Mon, Aug 17, 2026 at 11:00 PM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> On 8/18/26 02:59, KernelCI bot wrote:
> > New build issue found on mainline/master:
> >
> > ---
> >  in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile.build:435) [logspec:kbuild,kbuild.compiler]
> > ---
> >
> > Log excerpt:
> > =====================================================
>
> Missing for some reason. See below for one, grabbed it from
> https://d.kernelci.org/log-viewer?itemId=maestro%3A6a838f2962f33761c0d6680b&type=build&url=https%3A%2F%2Ffiles.kernelci.org%2Fkbuild-clang-21-arm-allmodconfig-6a838f2962f33761c0d6680b%2Fbuild.log.gz
>
> 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.

> make[5]: *** [/tmp/kci/linux/scripts/Makefile.build:435:
> arch/arm/kernel/entry-common.o] Error 1
> make[5]: Target 'arch/arm/kernel/' not remade because of errors.
> make[4]: *** [/tmp/kci/linux/scripts/Makefile.build:549:
> arch/arm/kernel] Error 2
> make[4]: Target 'arch/arm/' not remade because of errors.
> make[3]: *** [/tmp/kci/linux/scripts/Makefile.build:549: arch/arm] Error 2
> make[3]: Target './' not remade because of errors.
> make[2]: *** [/tmp/kci/linux/Makefile:2187: .] Error 2
> make[2]: Target '__all' not remade because of errors.
> make[1]: *** [/tmp/kci/linux/Makefile:248: __sub-make] Error 2
> make[1]: Target '__all' not remade because of errors.
> make: *** [Makefile:248: __sub-make] Error 2
> make: Target '__all' not remade because of errors.
> """
> Ciao, Thorsten
>
>
> > =====================================================
> >
> > When fixing this issue, please attribute this report according to the
> > patch submission rules:
> >
> > Reported-by: kernelci.org bot <bot@kernelci.org>
> > Link: https://lore.kernel.org/all/178701474442.5156.12765087253678603047@kernelci.org/
> >
> > For complete logs and details about the environment used, see the issue
> > on the KernelCI dashboard:
> >
> > - dashboard: https://d.kernelci.org/i/maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03
> > - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > - commit HEAD:  ff68e5f557f69a08fdcfa4ce8b1b809d63bd4f45
> >
> > # Builds where the incident occurred:
> >
> > ## defconfig+allmodconfig+CONFIG_FRAME_WARN=2048 on (arm):
> > - compiler: clang-21
> > - config: None
> > - dashboard: https://d.kernelci.org/build/maestro:6a838f2962f33761c0d6680b
> >
> > #regzbot introduced: 8d3ae59288f1e7d58d76558a6ee96d533bc5019f..ff68e5f557f69a08fdcfa4ce8b1b809d63bd4f45
> > #regzbot link: https://d.kernelci.org/i/maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03
> >
> > #kernelci issue maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03
> >
> > --
> > This is an experimental report format. Please send feedback in!
> > Talk to us at kernelci@lists.linux.dev
> >
> > Made with love by the KernelCI team - https://kernelci.org
> >
>


-- 
Thanks,
~Nick Desaulniers

Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]

On Tue, Aug 18, 2026 at 09:19:04AM -0700, Nick Desaulniers wrote:
> On Mon, Aug 17, 2026 at 11:00 PM Thorsten Leemhuis

> > 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).

It should be - that warning is just saying that tuxmake didn't directly
invoke docker/podman itself, this happens with KernelCI because the
builds are run in Kubernetes.

> What tree was being tested? 5fe41793bc78 landed in v5.18-rc1. Whatever
> was being tested is probably missing that patch.

The original mail has:

| For complete logs and details about the environment used, see the issue
| on the KernelCI dashboard:

| - dashboard: https://d.kernelci.org/i/maestro:5d5ba40a9374919c6038ec3e50f54dbe70a37c03
| - giturl: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
| - commit HEAD:  ff68e5f557f69a08fdcfa4ce8b1b809d63bd4f45

which is a recent merge in mainline.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[Nathan Chancellor]

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").

  # bad: [0f23d56f17fdfc7db69d51f64c8b91bbab947aa9] Merge tag 'linux_kselftest-next-7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
  # good: [8d3ae59288f1e7d58d76558a6ee96d533bc5019f] Linux 7.2
  git bisect start '0f23d56f17fdfc7db69d51f64c8b91bbab947aa9' 'v7.2'
  # bad: [1c3e8cef79ea5f1415cff0d3c507e2e07b71ade8] Merge tag 'vfs-7.3-rc1.misc' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs
  git bisect bad 1c3e8cef79ea5f1415cff0d3c507e2e07b71ade8
  # bad: [9ea8d6197d9f43a15ccb9c0dce601ec535d5da7e] Merge tag 'vfs-7.3-rc1.iomap' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs
  git bisect bad 9ea8d6197d9f43a15ccb9c0dce601ec535d5da7e
  # good: [a7b880449ab1b2389b31ed9da703691dcac54655] binfmt_misc: carry pre-opened interpreters in struct binfmt_misc_interp
  git bisect good a7b880449ab1b2389b31ed9da703691dcac54655
  # good: [7c7fe554f40adac2a7f8d9b6d5886ca332edd496] docs: fix grammatical error in iomap docs
  git bisect good 7c7fe554f40adac2a7f8d9b6d5886ca332edd496
  # good: [d31a688a49a82a48e0434aee9d851e094270a6ee] Merge tags 'vfs-7.3-rc1.efs' and 'vfs-7.3-rc1.freevxfs' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs
  git bisect good d31a688a49a82a48e0434aee9d851e094270a6ee
  # bad: [a45a6605cd04f2e55c1650a49bdb05106ac07ccc] Documentation: add failfs documentation
  git bisect bad a45a6605cd04f2e55c1650a49bdb05106ac07ccc
  # good: [20370a5f5d9b1549ab3bf10a898b4e024b8841fa] fs: add fchroot()
  git bisect good 20370a5f5d9b1549ab3bf10a898b4e024b8841fa
  # bad: [79d27fd718545db4731691e0a77e51d27dc1a41e] arch: hookup fchroot() system call
  git bisect bad 79d27fd718545db4731691e0a77e51d27dc1a41e
  # good: [b1221afa31cc2daf6b83d72e45827cffb4e86aff] fs: support FD_FAILFS_ROOT in fchroot()
  git bisect good b1221afa31cc2daf6b83d72e45827cffb4e86aff
  # first 'bad' commit: [79d27fd718545db4731691e0a77e51d27dc1a41e] 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.

-- 
Cheers,
Nathan

Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[Nathan Chancellor]

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

Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[Ard Biesheuvel]

On Tue, 18 Aug 2026, at 20:52, Nathan Chancellor wrote:
> 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.
>

We're falling back to the mov_l asm macro in this case.

This is unfortunate, because the only reason to avoid these group
relocations is making allyesconfig work, now that LLD has caught up.

I did not manage to reproduce this, but if this is something we care
deeply about, we might tweak mov_l as below when COMPILE_TEST is set,
so that the literal pool is always in range.


--- a/arch/arm/include/asm/assembler.h
+++ b/arch/arm/include/asm/assembler.h
@@ -636,6 +636,12 @@
        .macro          mov_l, dst:req, imm:req, cond
        .if             __LINUX_ARM_ARCH__ < 7
        ldr\cond        \dst, =\imm
+#ifdef CONFIG_COMPILE_TEST
+       /* The literal may go out of range in pathological cases */
+       b               .L\@
+       .ltorg
+.L\@:
+#endif
        .else
        movw\cond       \dst, #:lower16:\imm
        movt\cond       \dst, #:upper16:\imm

Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[Nathan Chancellor]

On Wed, Aug 19, 2026 at 11:08:39AM +0300, Ard Biesheuvel wrote:
> We're falling back to the mov_l asm macro in this case.
> 
> This is unfortunate, because the only reason to avoid these group
> relocations is making allyesconfig work, now that LLD has caught up.
> 
> I did not manage to reproduce this, but if this is something we care
> deeply about, we might tweak mov_l as below when COMPILE_TEST is set,
> so that the literal pool is always in range.

I am not sure that we do, at least currently, since Arnd's patch to turn
off OABI compat for everything but StrongARM has now landed in mainline,
getting rid of the originally reported error. If this error comes back,
we could look at a better fix.

> --- a/arch/arm/include/asm/assembler.h
> +++ b/arch/arm/include/asm/assembler.h
> @@ -636,6 +636,12 @@
>         .macro          mov_l, dst:req, imm:req, cond
>         .if             __LINUX_ARM_ARCH__ < 7
>         ldr\cond        \dst, =\imm
> +#ifdef CONFIG_COMPILE_TEST
> +       /* The literal may go out of range in pathological cases */
> +       b               .L\@
> +       .ltorg
> +.L\@:
> +#endif
>         .else
>         movw\cond       \dst, #:lower16:\imm
>         movt\cond       \dst, #:upper16:\imm

-- 
Cheers,
Nathan

Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...

[Thorsten Leemhuis]

On 8/20/26 02:09, Nathan Chancellor wrote:
> On Wed, Aug 19, 2026 at 11:08:39AM +0300, Ard Biesheuvel wrote:
>> We're falling back to the mov_l asm macro in this case.
>>
>> This is unfortunate, because the only reason to avoid these group
>> relocations is making allyesconfig work, now that LLD has caught up.
>>
>> I did not manage to reproduce this, but if this is something we care
>> deeply about, we might tweak mov_l as below when COMPILE_TEST is set,
>> so that the literal pool is always in range.
> 
> I am not sure that we do, at least currently, since Arnd's patch to turn
> off OABI compat for everything but StrongARM has now landed in mainline,
> getting rid of the originally reported error.

Grea. Nathan, Ard, many thx for looking into this!

> If this error comes back, we could look at a better fix.

+1 -- not sure, but even that might only be worth it if more than just
one CI runs into the problem in a particular test case.

Ciao, Thorsten
>> --- a/arch/arm/include/asm/assembler.h
>> +++ b/arch/arm/include/asm/assembler.h
>> @@ -636,6 +636,12 @@
>>         .macro          mov_l, dst:req, imm:req, cond
>>         .if             __LINUX_ARM_ARCH__ < 7
>>         ldr\cond        \dst, =\imm
>> +#ifdef CONFIG_COMPILE_TEST
>> +       /* The literal may go out of range in pathological cases */
>> +       b               .L\@
>> +       .ltorg
>> +.L\@:
>> +#endif
>>         .else
>>         movw\cond       \dst, #:lower16:\imm
>>         movt\cond       \dst, #:upper16:\imm
> 

#regzbot resolve: commit 25900bd99d4d avoids this error by disabling
CONFIG_OABI_COMPAT for allmodconfig