[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160624153503.oeivkn7djnxdi5oq@treble>
Date: Fri, 24 Jun 2016 10:35:03 -0500
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Andy Lutomirski <luto@...nel.org>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
Borislav Petkov <bp@...en8.de>, Nadav Amit <nadav.amit@...il.com>,
Kees Cook <keescook@...omium.org>, Brian Gerst <brgerst@...il.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jann Horn <jann@...jh.net>, Heiko Carstens <heiko.carstens@...ibm.com>
Subject: Re: [PATCH v4 13/16] x86/dumpstack: Try harder to get a call trace
on stack overflow
On Thu, Jun 23, 2016 at 09:23:08PM -0700, Andy Lutomirski wrote:
> If we overflow the stack, print_context_stack will abort. Detect
> this case and rewind back into the valid part of the stack so that
> we can trace it.
>
> Signed-off-by: Andy Lutomirski <luto@...nel.org>
Reviewed-by: Josh Poimboeuf <jpoimboe@...hat.com>
--
Josh
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
