From: Peter Zijlstra <peterz@infradead.org>
To: Petr Pavlu <petr.pavlu@suse.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, mhiramat@kernel.org,
samitolvanen@google.com, x86@kernel.org,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG
Date: Wed, 5 Jul 2023 10:52:22 +0200 [thread overview]
Message-ID: <20230705085222.GF462772@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230705081547.25130-2-petr.pavlu@suse.com>
On Wed, Jul 05, 2023 at 10:15:46AM +0200, Petr Pavlu wrote:
> Linker script arch/x86/kernel/vmlinux.lds.S matches the thunk sections
> ".text.__x86.*" from arch/x86/lib/retpoline.S as follows:
>
> .text {
> [...]
> TEXT_TEXT
> [...]
> __indirect_thunk_start = .;
> *(.text.__x86.*)
> __indirect_thunk_end = .;
> [...]
> }
>
> Macro TEXT_TEXT references TEXT_MAIN which normally expands to only
> ".text". However, with CONFIG_LTO_CLANG, TEXT_MAIN becomes
> ".text .text.[0-9a-zA-Z_]*" which wrongly matches also the thunk
> sections. The range [__indirect_thunk_start, __indirect_thunk_end] is
> then empty.
>
> A visible result is that function insn_is_indirect_jump() misbehaves and
> optprobes become allowed in functions where they are not potentially
> safe.
>
> Fix the problem by using ".." as the first separator, for instance,
> ".text..__x86.indirect_thunk". This pattern is utilized by other
First I hear of this, but yes, indeed.
> explicit section names which start with one of the standard prefixes,
> such as ".text" or ".data", and that need to be individually selected in
> the linker script.
>
> Fixes: dc5723b02e52 ("kbuild: add support for Clang LTO")
> Signed-off-by: Petr Pavlu <petr.pavlu@suse.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> arch/x86/kernel/vmlinux.lds.S | 2 +-
> arch/x86/lib/retpoline.S | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S
> index 03c885d3640f..a4cd04c458df 100644
> --- a/arch/x86/kernel/vmlinux.lds.S
> +++ b/arch/x86/kernel/vmlinux.lds.S
> @@ -134,7 +134,7 @@ SECTIONS
> SOFTIRQENTRY_TEXT
> #ifdef CONFIG_RETPOLINE
> __indirect_thunk_start = .;
> - *(.text.__x86.*)
> + *(.text..__x86.*)
> __indirect_thunk_end = .;
> #endif
> STATIC_CALL_TEXT
> diff --git a/arch/x86/lib/retpoline.S b/arch/x86/lib/retpoline.S
> index 3fd066d42ec0..3bea96341d00 100644
> --- a/arch/x86/lib/retpoline.S
> +++ b/arch/x86/lib/retpoline.S
> @@ -12,7 +12,7 @@
> #include <asm/percpu.h>
> #include <asm/frame.h>
>
> - .section .text.__x86.indirect_thunk
> + .section .text..__x86.indirect_thunk
>
>
> .macro POLINE reg
> @@ -131,7 +131,7 @@ SYM_CODE_END(__x86_indirect_jump_thunk_array)
> */
> #ifdef CONFIG_RETHUNK
>
> - .section .text.__x86.return_thunk
> + .section .text..__x86.return_thunk
>
> /*
> * Safety details here pertain to the AMD Zen{1,2} microarchitecture:
> --
> 2.35.3
>
next prev parent reply other threads:[~2023-07-05 8:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 8:15 [PATCH 0/2] x86/retpoline,kprobes: Fix the [__indirect_thunk_start, ..end] range Petr Pavlu
2023-07-05 8:15 ` [PATCH 1/2] x86/retpoline,kprobes: Fix position of thunk sections with CONFIG_LTO_CLANG Petr Pavlu
2023-07-05 8:52 ` Peter Zijlstra [this message]
2023-07-05 8:15 ` [PATCH 2/2] x86/retpoline,kprobes: Avoid treating rethunk as an indirect jump Petr Pavlu
2023-07-05 8:58 ` Peter Zijlstra
2023-07-05 14:20 ` Masami Hiramatsu
2023-07-05 14:50 ` Peter Zijlstra
2023-07-06 0:47 ` Masami Hiramatsu
2023-07-06 7:17 ` Peter Zijlstra
2023-07-06 9:00 ` Masami Hiramatsu
2023-07-06 11:34 ` Peter Zijlstra
2023-07-07 14:39 ` Masami Hiramatsu
2023-07-08 14:18 ` Petr Pavlu
2023-07-09 15:25 ` Masami Hiramatsu
2023-07-05 9:02 ` Peter Zijlstra
2023-07-05 14:40 ` Masami Hiramatsu
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=20230705085222.GF462772@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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