From: Nathan Chancellor <nathan@kernel.org>
To: Jens Remus <jremus@linux.ibm.com>
Cc: Sami Tolvanen <samitolvanen@google.com>,
Kees Cook <kees@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
Heiko Carstens <hca@linux.ibm.com>,
Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH] x86/cfi: Use symmetric SYM_START and SYM_END in __CFI_TYPE()
Date: Sat, 13 Jun 2026 12:29:23 -0400 [thread overview]
Message-ID: <20260613162923.GB2697431@ax162> (raw)
In-Reply-To: <20260611155716.830563-1-jremus@linux.ibm.com>
On Thu, Jun 11, 2026 at 05:57:15PM +0200, Jens Remus wrote:
> Commit ccace936eec7 ("x86: Add types to indirectly called assembly
> functions") introduced a x86-specific implementation of __CFI_TYPE()
> using an asymmetric combination of SYM_START() and SYM_FUNC_END() to
> add a symbol to the KCFI type identifier that precedes a function.
>
> This asymmetric combination is an issue if SYM_FUNC_END() ever gets
> extended in a way that requires it to be used symmetrically with
> SYM_FUNC_START*(). For instance to emit DWARF CFI directives that
> denote the start/end of a function. [1]
>
> Use SYM_END() with SYM_T_FUNC instead. No functional change, as the
> generic implementation of SYM_FUNC_END(name) expands into
> SYM_END(name, SYM_T_FUNC).
>
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Closes: https://sashiko.dev/#/patchset/20260522110427.2816637-1-jremus@linux.ibm.com?part=3 [1]
> Signed-off-by: Jens Remus <jremus@linux.ibm.com>
Reviewed-by: Nathan Chancellor <nathan@kernel.org>
> ---
>
> Notes (jremus):
> This patch applies on top of linus' tree (9716c086c8e8):
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> I verified as follows that in x86-64 builds of vmlinux using Clang with
> kCFI enabled without and with my patch applied vmlinux.o only differs in
> relocations targeting .rodata.str* and a few symbols in .rodata shifted
> (both likely due to differences in string merging):
>
> $ objdump -d vmlinux.o > vmlinux.o.{old|new}.objdump
> $ readelf -Wa vmlinux.o > vmlinux.o.{old|new}.readelf
> $ diff -u vmlinux.o.old.objdump vmlinux.o.new.objdump
> [no differences]
> $ diff -u0 vmlinux.o.old.readelf vmlinux.o.new.readelf | \
> grep --invert-match -E "\.rodata\.str|@@"
> [see above]
>
> arch/x86/include/asm/linkage.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/include/asm/linkage.h b/arch/x86/include/asm/linkage.h
> index a7294656ad90..c9769a7b6e66 100644
> --- a/arch/x86/include/asm/linkage.h
> +++ b/arch/x86/include/asm/linkage.h
> @@ -103,7 +103,7 @@
> .byte 0xb8 ASM_NL \
> .long __kcfi_typeid_##name ASM_NL \
> CFI_POST_PADDING \
> - SYM_FUNC_END(__cfi_##name)
> + SYM_END(__cfi_##name, SYM_T_FUNC)
>
> /* UML needs to be able to override memcpy() and friends for KASAN. */
> #ifdef CONFIG_UML
> --
> 2.53.0
>
--
Cheers,
Nathan
next prev parent reply other threads:[~2026-06-13 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 15:57 [PATCH] x86/cfi: Use symmetric SYM_START and SYM_END in __CFI_TYPE() Jens Remus
2026-06-11 19:28 ` Peter Zijlstra
2026-06-13 16:29 ` Nathan Chancellor [this message]
2026-06-28 23:14 ` [tip: x86/cleanups] " tip-bot2 for Jens Remus
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=20260613162923.GB2697431@ax162 \
--to=nathan@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=jremus@linux.ibm.com \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=sashiko-bot@kernel.org \
--cc=tglx@kernel.org \
--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