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>
Subject: Re: [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile...
Date: Tue, 18 Aug 2026 09:51:16 -0700 [thread overview]
Message-ID: <20260818165116.GA1335107@ax162> (raw)
In-Reply-To: <CAKwvOdkcCnhM-395QVriu3hnjmtX1H-3i_1tU5Jpb1Ybr2Q77g@mail.gmail.com>
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
next prev parent reply other threads:[~2026-08-18 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 0:59 [REGRESSION] mainline/master: (build) in arch/arm/kernel/entry-common.o (/tmp/kci/linux/scripts/Makefile KernelCI bot
2026-08-18 6:00 ` Thorsten Leemhuis
2026-08-18 16:19 ` Nick Desaulniers
2026-08-18 16:28 ` Mark Brown
2026-08-18 16:51 ` Nathan Chancellor [this message]
2026-08-18 17:52 ` Nathan Chancellor
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=20260818165116.GA1335107@ax162 \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--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 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.