From: "Schimpe, Christina via Gdb" <gdb@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>,
"Schimpe, Christina via Gdb" <gdb@sourceware.org>
Cc: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
Tom Tromey <tom@tromey.com>
Subject: RE: Shadow stack backtrace command name
Date: Tue, 9 Jul 2024 14:50:28 +0000 [thread overview]
Message-ID: <SN7PR11MB7638F4A41C79AC2DD80E756DF9DB2@SN7PR11MB7638.namprd11.prod.outlook.com> (raw)
In-Reply-To: <874j93vh4w.fsf@oldenburg.str.redhat.com>
> * Christina via Gdb Schimpe:
>
> > However, based on the use cases that I am aware of, I am not sure if
> > the user wants to always see the shadow stack bt in the ordinary bt
> > output (if shadow stack is enabled).
>
> Based on my experiments, Linux currently does not push the instruction
> pointer onto the shadow stack if code is interrupted by a signal. It still works
> because the return mechanism is different. This would be a very visible
> difference between ordinary backtraces and shadow stack based backtraces.
> As far as I understand it, the kernel could change, and it may still be early
> enough to make this change.
Could you explain a bit why and what you think the kernel will change ?
Just to be sure that I understand correctly:
Do you think that this different display for the ordinary and shadow stack bt in
case of signals is one argument more for displaying the stacks together?
How would this look like?
> By the way, is there a way to tell if a process is in shadow stack mode using
> upstream GDB today? Preferably something that does not rely on glibc
> internals?
You can run "info proc status" and check for "shstk" in x86_Thread_features, see
https://docs.kernel.org/arch/x86/shstk.html.
Christina
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Sean Fennelly, Jeffrey Schneiderman, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2024-07-09 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 9:42 Schimpe, Christina via Gdb
2023-12-20 10:59 ` Guinevere Larsen via Gdb
2023-12-20 15:11 ` Schimpe, Christina via Gdb
2023-12-20 11:38 ` Luis Machado via Gdb
2023-12-20 15:35 ` Schimpe, Christina via Gdb
2023-12-20 15:57 ` Luis Machado via Gdb
2023-12-21 4:35 ` Thiago Jung Bauermann via Gdb
2023-12-21 22:26 ` Shadow stack command to host related subcommands (was Re: Shadow stack backtrace command name) Thiago Jung Bauermann via Gdb
2024-01-09 8:34 ` Schimpe, Christina via Gdb
2023-12-23 18:22 ` Shadow stack backtrace command name Tom Tromey
2023-12-28 22:34 ` Thiago Jung Bauermann via Gdb
2024-01-09 10:21 ` Schimpe, Christina via Gdb
2024-07-05 18:16 ` Florian Weimer via Gdb
2024-07-09 14:50 ` Schimpe, Christina via Gdb [this message]
2024-07-09 15:16 ` Florian Weimer via Gdb
2024-07-10 9:07 ` Schimpe, Christina via Gdb
2024-07-10 10:05 ` Florian Weimer via Gdb
2024-07-10 11:35 ` Schimpe, Christina via Gdb
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=SN7PR11MB7638F4A41C79AC2DD80E756DF9DB2@SN7PR11MB7638.namprd11.prod.outlook.com \
--to=gdb@sourceware.org \
--cc=christina.schimpe@intel.com \
--cc=fweimer@redhat.com \
--cc=thiago.bauermann@linaro.org \
--cc=tom@tromey.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