From: Jens Remus <jremus@linux.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Indu Bhagat <indu.bhagat@oracle.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Indu Bhagat <indu.bhagat@oracle.com>,
Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 6/6] x86/vdso: Enable sframe generation in VDSO
Date: Mon, 20 Oct 2025 16:06:13 +0200 [thread overview]
Message-ID: <31167d13-abfb-44c3-8999-02132a8b495d@linux.ibm.com> (raw)
In-Reply-To: <20250425024023.173709192@goodmis.org>
On 4/25/2025 4:37 AM, Steven Rostedt wrote:
> From: Josh Poimboeuf <jpoimboe@kernel.org>
>
> Enable sframe generation in the VDSO library so kernel and user space
> can unwind through it.
>
> Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> diff --git a/arch/x86/entry/vdso/vdso-layout.lds.S b/arch/x86/entry/vdso/vdso-layout.lds.S
> @@ -87,6 +88,7 @@ SECTIONS
> * Very old versions of ld do not recognize this name token; use the constant.
> */
> #define PT_GNU_EH_FRAME 0x6474e550
> +#define PT_GNU_SFRAME 0x6474e554
>
> /*
> * We must supply the ELF program headers explicitly to get just one
> @@ -98,4 +100,5 @@ PHDRS
> dynamic PT_DYNAMIC FLAGS(4); /* PF_R */
> note PT_NOTE FLAGS(4); /* PF_R */
> eh_frame_hdr PT_GNU_EH_FRAME;
On s390 I found that the respective s390-change needs to be guarded to
prevent the vDSO from erroneously getting generated with a bogus
GNU_SFRAME program table entry, if CONFIG_AS_SFRAME is not enabled:
$ readelf -Wl arch/s390/kernel/vdso64/vdso64.so
...
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
LOAD 0x000000 0x0000000000000000 0x0000000000000000 0x001508 0x001508 R E 0x1000
DYNAMIC 0x001190 0x0000000000001190 0x0000000000001190 0x000100 0x000100 R 0x8
NOTE 0x000420 0x0000000000000420 0x0000000000000420 0x00003c 0x00003c R 0x4
GNU_EH_FRAME 0x000000 0x0000000000000000 0x0000000000000000 0x000000 0x000000 0x8
GNU_SFRAME 0x0014f0 0x00000000000014f0 0x00000000000014f0 0x000018 0x000018 RW 0x8
...
$ xxd arch/s390/kernel/vdso64/vdso64.so
...
000014f0: 0000 0000 0000 1190 0000 0000 0000 0000 ................
00001500: 0000 0000 0000 0000 4743 433a 2028 5562 ........GCC: (Ub
00001510: 756e 7475 2031 342e 322e 302d 3139 7562 untu 14.2.0-19ub
00001520: 756e 7475 3229 2031 342e 322e 3000 0000 untu2) 14.2.0...
...
Following would be the guard for x86 (same as the one used below in
arch/x86/include/asm/dwarf2.h):
#if defined(__x86_64__) && defined(CONFIG_AS_SFRAME)
> + sframe PT_GNU_SFRAME;
#endif
> }
> diff --git a/arch/x86/include/asm/dwarf2.h b/arch/x86/include/asm/dwarf2.h
> @@ -12,8 +12,11 @@
> * For the vDSO, emit both runtime unwind information and debug
> * symbols for the .dbg file.
> */
> -
> +#if defined(__x86_64__) && defined(CONFIG_AS_SFRAME)
> + .cfi_sections .eh_frame, .debug_frame, .sframe
> +#else
> .cfi_sections .eh_frame, .debug_frame
> +#endif
>
> #define CFI_STARTPROC .cfi_startproc
> #define CFI_ENDPROC .cfi_endproc
Regards,
Jens
--
Jens Remus
Linux on Z Development (D3303)
+49-7031-16-1128 Office
jremus@de.ibm.com
IBM
IBM Deutschland Research & Development GmbH; Vorsitzender des Aufsichtsrats: Wolfgang Wendt; Geschäftsführung: David Faller; Sitz der Gesellschaft: Böblingen; Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM Data Privacy Statement: https://www.ibm.com/privacy/
next prev parent reply other threads:[~2025-10-20 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 2:37 [PATCH 0/6] [PATCH v6 0/6] x86/vdso: VDSO updates and fixes for sframes Steven Rostedt
2025-04-25 2:37 ` [PATCH 1/6] x86/vdso: Fix DWARF generation for getrandom() Steven Rostedt
2025-04-25 2:37 ` [PATCH 2/6] x86/asm: Avoid emitting DWARF CFI for non-VDSO Steven Rostedt
2025-04-25 2:37 ` [PATCH 3/6] x86/asm: Use CFI_* macros in SYM_FUNC_* macros so they can be added to VDSO Steven Rostedt
2025-04-25 2:37 ` [PATCH 4/6] x86/vdso: Use SYM_FUNC_{START,END} in __kernel_vsyscall() Steven Rostedt
2025-04-25 2:37 ` [PATCH 5/6] x86/vdso: Use CFI macros in __vdso_sgx_enter_enclave() Steven Rostedt
2025-04-25 23:22 ` Indu Bhagat
2025-04-28 16:16 ` Josh Poimboeuf
2025-04-28 17:10 ` Josh Poimboeuf
2025-04-29 17:52 ` Indu Bhagat
2025-04-28 16:23 ` Josh Poimboeuf
2025-04-25 2:37 ` [PATCH 6/6] x86/vdso: Enable sframe generation in VDSO Steven Rostedt
2025-05-27 14:16 ` Jens Remus
2025-10-20 14:06 ` Jens Remus [this message]
2025-04-25 14:47 ` [PATCH 0/6] [PATCH v6 0/6] x86/vdso: VDSO updates and fixes for sframes Steven Rostedt
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=31167d13-abfb-44c3-8999-02132a8b495d@linux.ibm.com \
--to=jremus@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=indu.bhagat@oracle.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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
all inboxes | Powered by JetHome®