From: Nathan Chancellor <nathan@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk,
Nick Desaulniers <ndesaulniers@google.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] ARM: entry: add .ltorg directive to keep literals in range
Date: Tue, 31 May 2022 08:29:01 -0700 [thread overview]
Message-ID: <YpY0PbvRvuA7OU//@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20220530112417.2492510-1-ardb@kernel.org>
On Mon, May 30, 2022 at 01:24:17PM +0200, Ard Biesheuvel wrote:
> LKP reports a build issue on Clang, related to a literal load of
> __current issued through the ldr_va macro. This turns out to be due to
> the fact that group relocations are disabled when CONFIG_COMPILE_TEST=y,
> which means that the ldr_va macro resolves to a pair of LDR
> instructions, the first one being a literal load issued too far from its
> literal pool.
For the record, I do see a similar failure with GNU as, not sure if it
is worth calling that out in the commit message or not:
arch/arm/kernel/entry-common.S: Assembler messages:
arch/arm/kernel/entry-common.S:149: Error: invalid literal constant: pool needs to be closer
> Due to the introduction of a couple of new uses of this macro in commit
> 508074607c7b95b2 ("ARM: 9195/1: entry: avoid explicit literal loads"),
> the literal pools end up getting rearranged in a way that causes the
> literal for __current to go out of range. Let's fix this up by putting a
> .ltorg directive in a suitable place in the code.
>
> Cc: Nathan Chancellor <nathan@kernel.org>
> Cc: Nick Desaulniers <ndesaulniers@google.com>
> Fixes: 508074607c7b95b2 ("ARM: 9195/1: entry: avoid explicit literal loads")
> Reported-by: kernel test robot <lkp@intel.com>
> Link: https://lore.kernel.org/all/202205290805.1vZLAr36-lkp@intel.com/
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
With the problematic configuration, I no longer see issues with either
clang or GCC:
Tested-by: Nathan Chancellor <nathan@kernel.org>
> ---
> arch/arm/kernel/entry-common.S | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/kernel/entry-common.S b/arch/arm/kernel/entry-common.S
> index 7aa3ded4af92..6a447ac67d80 100644
> --- a/arch/arm/kernel/entry-common.S
> +++ b/arch/arm/kernel/entry-common.S
> @@ -298,14 +298,15 @@ local_restart:
> 9001:
> sub lr, saved_pc, #4
> str lr, [sp, #S_PC]
> get_thread_info tsk
> b ret_fast_syscall
> #endif
> ENDPROC(vector_swi)
> + .ltorg
>
> /*
> * This is the really slow path. We're going to be doing
> * context switches, and waiting for our parent to respond.
> */
> __sys_trace:
> add r0, sp, #S_OFF
> --
> 2.30.2
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-31 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 11:24 [PATCH] ARM: entry: add .ltorg directive to keep literals in range Ard Biesheuvel
2022-05-31 15:29 ` Nathan Chancellor [this message]
2022-06-01 11:35 ` Ard Biesheuvel
2022-06-08 18:42 ` Nick Desaulniers
2022-06-08 20:29 ` Ard Biesheuvel
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=YpY0PbvRvuA7OU//@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=ndesaulniers@google.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