From: Josh Poimboeuf <jpoimboe@kernel.org>
To: David Laight <David.Laight@aculab.com>
Cc: 'Peter Zijlstra' <peterz@infradead.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>,
Michael Matz <matz@suse.de>,
"linux-toolchains@vger.kernel.org"
<linux-toolchains@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH] x86/sev: Mark snp_abort() noreturn
Date: Mon, 29 Aug 2022 21:48:11 -0700 [thread overview]
Message-ID: <20220830044811.jad66k4sxdfnprul@treble> (raw)
In-Reply-To: <ce56926842dc49ecb08ddb9d828590af@AcuMS.aculab.com>
On Thu, Aug 25, 2022 at 01:12:42PM +0000, David Laight wrote:
> ...
> > Objtool follows control flow. As you said above, noreturn functions
> > behave differently and code-gen after a call to a noreturn function
> > stops.
>
> Thinks....
>
> How near is objtool to outputting a list of functions and the
> stack offset at which they call something else?
It basically already does this.
> With the 'magic numbers' to track indirect jumps that is very
> nearly enough information to do full static stack depth checking.
What do you mean by 'magic numbers'?
--
Josh
next prev parent reply other threads:[~2022-08-30 4:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 15:24 [PATCH] x86/sev: Mark snp_abort() noreturn Borislav Petkov
2022-08-24 15:38 ` Peter Zijlstra
2022-08-24 15:48 ` Borislav Petkov
2022-08-24 16:16 ` Peter Zijlstra
2022-08-24 16:43 ` [PATCH v2] " Borislav Petkov
2022-08-24 17:29 ` [PATCH] " Segher Boessenkool
2022-08-24 18:23 ` Borislav Petkov
2022-08-24 18:44 ` Nick Desaulniers
2022-08-24 19:43 ` Segher Boessenkool
2022-08-24 20:45 ` Peter Zijlstra
2022-08-24 22:41 ` Segher Boessenkool
2022-08-25 6:41 ` Peter Zijlstra
2022-08-25 12:29 ` Michael Matz
2022-08-25 12:58 ` Segher Boessenkool
2022-08-25 13:12 ` David Laight
2022-08-30 4:48 ` Josh Poimboeuf [this message]
2022-08-30 4:46 ` Josh Poimboeuf
2022-08-25 14:01 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov
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=20220830044811.jad66k4sxdfnprul@treble \
--to=jpoimboe@kernel.org \
--cc=David.Laight@aculab.com \
--cc=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=matz@suse.de \
--cc=peterz@infradead.org \
--cc=segher@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.