x86/unwind: Detect bad stack return address
authorJosh Poimboeuf <[email protected]>
Wed, 26 Oct 2016 15:41:51 +0000 (10:41 -0500)
committerIngo Molnar <[email protected]>
Thu, 27 Oct 2016 06:32:38 +0000 (08:32 +0200)
commitb6959a362177053c1c90db6dc1af25b6bddd8548
tree130057c49063003c48dca7d8697a3726c59d644b
parent0d2b8579add41e08aa1110da864f1071d58e6048
x86/unwind: Detect bad stack return address

If __kernel_text_address() doesn't recognize a return address on the
stack, it probably means that it's some generated code which
__kernel_text_address() doesn't know about yet.

Otherwise there's probably some stack corruption.

Either way, warn about it.

Use printk_deferred_once() because the unwinder can be called with the
console lock by lockdep via save_stack_trace().

Signed-off-by: Josh Poimboeuf <[email protected]>
Cc: Andy Lutomirski <[email protected]>
Cc: Borislav Petkov <[email protected]>
Cc: Brian Gerst <[email protected]>
Cc: Denys Vlasenko <[email protected]>
Cc: H. Peter Anvin <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Link: http://lkml.kernel.org/r/2d897898f324e275943b590d160b55e482bba65f.1477496147.git.jpoimboe@redhat.com
Signed-off-by: Ingo Molnar <[email protected]>
arch/x86/kernel/unwind_frame.c