From: Andi Kleen Date: Fri, 13 Jan 2012 01:20:30 +0000 (-0800) Subject: panic: don't print redundant backtraces on oops X-Git-Url: https://openfabrics.org/gitweb/?a=commitdiff_plain;h=6e6f0a1f0fa6bba1493c296eb30d1e176e1f8530;p=~shefty%2Frdma-dev.git panic: don't print redundant backtraces on oops When an oops causes a panic and panic prints another backtrace it's pretty common to have the original oops data be scrolled away on a 80x50 screen. The second backtrace is quite redundant and not needed anyways. So don't print the panic backtrace when oops_in_progress is true. [akpm@linux-foundation.org: add comment] Signed-off-by: Andi Kleen Cc: Michael Holzheu Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds --- diff --git a/kernel/panic.c b/kernel/panic.c index 5dce5404eee..80aed44e345 100644 --- a/kernel/panic.c +++ b/kernel/panic.c @@ -94,7 +94,11 @@ void panic(const char *fmt, ...) va_end(args); printk(KERN_EMERG "Kernel panic - not syncing: %s\n",buf); #ifdef CONFIG_DEBUG_BUGVERBOSE - dump_stack(); + /* + * Avoid nested stack-dumping if a panic occurs during oops processing + */ + if (!oops_in_progress) + dump_stack(); #endif /*