From: Jens Remus <jremus@linux.ibm.com>
To: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org,
Steven Rostedt <rostedt@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrii Nakryiko <andrii@kernel.org>,
Indu Bhagat <indu.bhagat@oracle.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
Beau Belgrave <beaub@linux.microsoft.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Florian Weimer <fweimer@redhat.com>, Kees Cook <kees@kernel.org>,
"Carlos O'Donell" <codonell@redhat.com>,
Sam James <sam@gentoo.org>, Dylan Hatch <dylanbhatch@google.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: Re: [PATCH v7 2/6] x86/asm: Avoid emitting DWARF CFI for non-VDSO
Date: Fri, 6 Feb 2026 15:01:19 +0100 [thread overview]
Message-ID: <832897ac-f1d4-4f91-8034-f6b2d9e86fa4@linux.ibm.com> (raw)
In-Reply-To: <bd2fdf83-e460-46ad-8617-16319bc55ca5@zytor.com>
On 2/4/2026 1:43 AM, H. Peter Anvin wrote:
> On 2026-02-03 09:19, Jens Remus wrote:
>> From: Josh Poimboeuf <jpoimboe@kernel.org>
>>
>> It was decided years ago that .cfi_* annotations aren't maintainable in
>> the kernel. They were replaced by objtool unwind hints. For the kernel
>> proper, ensure the CFI_* macros don't do anything.
>>
>> On the other hand the VDSO library *does* use them, so user space can
>> unwind through it.
>>
>> Make sure these macros only work for VDSO. They aren't actually being
>> used outside of VDSO anyway, so there's no functional change.
>>
>> Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
>> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
>> Signed-off-by: Jens Remus <jremus@linux.ibm.com>
>> ---
>> arch/x86/include/asm/dwarf2.h | 51 ++++++++++++++++++++++++-----------
>> 1 file changed, 35 insertions(+), 16 deletions(-)
>>
>> diff --git a/arch/x86/include/asm/dwarf2.h b/arch/x86/include/asm/dwarf2.h
>> index 09c9684d3ad6..7cc30500c095 100644
>> --- a/arch/x86/include/asm/dwarf2.h
>> +++ b/arch/x86/include/asm/dwarf2.h
>> @@ -6,6 +6,15 @@
>> #warning "asm/dwarf2.h should be only included in pure assembly files"
>> #endif
>>
>> +#ifdef BUILD_VDSO
>> +
>> + /*
>> + * For the vDSO, emit both runtime unwind information and debug
>> + * symbols for the .dbg file.
>> + */
>> +
>> + .cfi_sections .eh_frame, .debug_frame
>> +
>> #define CFI_STARTPROC .cfi_startproc
>> #define CFI_ENDPROC .cfi_endproc
>> #define CFI_DEF_CFA .cfi_def_cfa
>> @@ -22,21 +31,31 @@
>> #define CFI_ESCAPE .cfi_escape
>> #define CFI_SIGNAL_FRAME .cfi_signal_frame
I missed that this is new on tip:x86/entry and thus also needs to be
added below in the !BUILD_VDSO case.
>>
>> -#ifndef BUILD_VDSO
>> - /*
>> - * Emit CFI data in .debug_frame sections, not .eh_frame sections.
>> - * The latter we currently just discard since we don't do DWARF
>> - * unwinding at runtime. So only the offline DWARF information is
>> - * useful to anyone. Note we should not use this directive if we
>> - * ever decide to enable DWARF unwinding at runtime.
>> - */
>> - .cfi_sections .debug_frame
>> -#else
>> - /*
>> - * For the vDSO, emit both runtime unwind information and debug
>> - * symbols for the .dbg file.
>> - */
>> - .cfi_sections .eh_frame, .debug_frame
>> -#endif
>> +#else /* !BUILD_VDSO */
>> +
>> +/*
>> + * On x86, these macros aren't used outside VDSO. As well they shouldn't be:
>> + * they're fragile and very difficult to maintain.
>> + */
>> +
>> +.macro nocfi args:vararg
>> +.endm
>> +
>> +#define CFI_STARTPROC nocfi
>> +#define CFI_ENDPROC nocfi
>> +#define CFI_DEF_CFA nocfi
>> +#define CFI_DEF_CFA_REGISTER nocfi
>> +#define CFI_DEF_CFA_OFFSET nocfi
>> +#define CFI_ADJUST_CFA_OFFSET nocfi
>> +#define CFI_OFFSET nocfi
>> +#define CFI_REL_OFFSET nocfi
>> +#define CFI_REGISTER nocfi
>> +#define CFI_RESTORE nocfi
>> +#define CFI_REMEMBER_STATE nocfi
>> +#define CFI_RESTORE_STATE nocfi
>> +#define CFI_UNDEFINED nocfi
>> +#define CFI_ESCAPE nocfi
#define CFI_SIGNAL_FRAME nocfi
>> +
>> +#endif /* !BUILD_VDSO */
>>
>> #endif /* _ASM_X86_DWARF2_H */
>
> I guess patch 3 justifies this.
>
> Acked-by: H. Peter Anvin (Intel) <hpa@zytor.com>
>
Regards,
Jens
--
Jens Remus
Linux on Z Development (D3303)
jremus@de.ibm.com / jremus@linux.ibm.com
IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der Gesellschaft: Ehningen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/
next prev parent reply other threads:[~2026-02-06 14:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:19 [PATCH v7 0/6] x86/vdso: VDSO updates and fixes for sframes Jens Remus
2026-02-03 17:19 ` [PATCH v7 1/6] x86/vdso: Fix DWARF generation for getrandom() Jens Remus
2026-02-04 0:43 ` H. Peter Anvin
2026-02-03 17:19 ` [PATCH v7 2/6] x86/asm: Avoid emitting DWARF CFI for non-VDSO Jens Remus
2026-02-03 17:35 ` H. Peter Anvin
2026-02-04 0:43 ` H. Peter Anvin
2026-02-06 14:01 ` Jens Remus [this message]
2026-02-03 17:19 ` [PATCH v7 3/6] x86/asm: Simplify VDSO DWARF generation Jens Remus
2026-02-04 0:44 ` H. Peter Anvin
2026-02-03 17:19 ` [PATCH v7 4/6] x86/vdso: Use SYM_FUNC_{START,END} in __kernel_vsyscall() Jens Remus
2026-02-04 0:44 ` H. Peter Anvin
2026-02-03 17:19 ` [PATCH v7 5/6] x86/vdso: Use CFI macros in __vdso_sgx_enter_enclave() Jens Remus
2026-02-04 0:44 ` H. Peter Anvin
2026-02-06 15:04 ` Jens Remus
2026-02-03 17:19 ` [PATCH v7 6/6] x86/vdso: Enable sframe generation in VDSO Jens Remus
2026-02-04 0:49 ` H. Peter Anvin
2026-02-06 17:48 ` Jens Remus
2026-02-06 23:56 ` H. Peter Anvin
2026-02-07 0:48 ` Josh Poimboeuf
2026-02-06 15:02 ` [PATCH v7 0/6] x86/vdso: VDSO updates and fixes for sframes 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=832897ac-f1d4-4f91-8034-f6b2d9e86fa4@linux.ibm.com \
--to=jremus@linux.ibm.com \
--cc=Liam.Howlett@oracle.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=bp@alien8.de \
--cc=bpf@vger.kernel.org \
--cc=codonell@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dylanbhatch@google.com \
--cc=fweimer@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=indu.bhagat@oracle.com \
--cc=jemarch@gnu.org \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rostedt@kernel.org \
--cc=rppt@kernel.org \
--cc=sam@gentoo.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--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