[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ce56926842dc49ecb08ddb9d828590af@AcuMS.aculab.com>
Date: Thu, 25 Aug 2022 13:12:42 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Peter Zijlstra' <peterz@...radead.org>,
Segher Boessenkool <segher@...nel.crashing.org>
CC: Borislav Petkov <bp@...en8.de>, X86 ML <x86@...nel.org>,
Michael Matz <matz@...e.de>,
"linux-toolchains@...r.kernel.org" <linux-toolchains@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
"Josh Poimboeuf" <jpoimboe@...hat.com>
Subject: RE: [PATCH] x86/sev: Mark snp_abort() noreturn
...
> 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?
With the 'magic numbers' to track indirect jumps that is very
nearly enough information to do full static stack depth checking.
Recursive calls are a problem - but they ought to be banned
in kernel anyway.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists