[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f30ce279-35fa-e113-a138-c2d553a983cb@zytor.com>
Date: Mon, 15 Aug 2016 11:04:42 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Josh Poimboeuf <jpoimboe@...hat.com>,
Andy Lutomirski <luto@...capital.net>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>, X86 ML <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Steven Rostedt <rostedt@...dmis.org>,
Brian Gerst <brgerst@...il.com>,
Kees Cook <keescook@...omium.org>,
Peter Zijlstra <peterz@...radead.org>,
Frederic Weisbecker <fweisbec@...il.com>,
Byungchul Park <byungchul.park@....com>,
Nilay Vaish <nilayvaish@...il.com>
Subject: Re: [PATCH v3 16/51] x86/32: put real return address on stack in
entry code
On 08/15/16 08:09, Josh Poimboeuf wrote:
> On Sun, Aug 14, 2016 at 12:31:47AM -0700, Andy Lutomirski wrote:
>> On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf <jpoimboe@...hat.com> wrote:
>>> This standardizes the stacks of idle tasks to be consistent with other
>>> tasks on 32-bit.
>>
>> It might be nice to stick a ud2 or 1: hlt; jmp 1b or similar
>> afterwards to make it clear that initial_code can't return.
>
> Yeah, I'll do something like that.
>
"Standardizing the stack" how? A zero on the stack terminates the stack
trace.
-hpa
Powered by blists - more mailing lists