panic: don't print redundant backtraces on oops
authorAndi Kleen <ak@linux.intel.com>
Fri, 13 Jan 2012 01:20:30 +0000 (17:20 -0800)
committerLinus Torvalds <torvalds@linux-foundation.org>
Fri, 13 Jan 2012 04:13:11 +0000 (20:13 -0800)
commit6e6f0a1f0fa6bba1493c296eb30d1e176e1f8530
treec1bbacbc93e5b6f7759d509d7cf6207ad5b3ee65
parentb8f566b04d3cddd192cfd2418ae6d54ac6353792
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 <ak@linux.intel.com>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
kernel/panic.c