| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1323304603-27895-1-git-send-email-andi@firstfloor.org> Date: Wed, 7 Dec 2011 16:36:43 -0800 From: Andi Kleen <andi@...stfloor.org> To: linux-kernel@...r.kernel.org Cc: Andi Kleen <ak@...ux.intel.com> Subject: [PATCH] panic: Don't print redundant backtraces on oops From: Andi Kleen <ak@...ux.intel.com> 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. Signed-off-by: Andi Kleen <ak@...ux.intel.com> --- kernel/panic.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/kernel/panic.c b/kernel/panic.c index b2659360..398412b 100644 --- a/kernel/panic.c +++ b/kernel/panic.c @@ -78,7 +78,8 @@ NORET_TYPE void panic(const char * fmt, ...) va_end(args); printk(KERN_EMERG "Kernel panic - not syncing: %s\n",buf); #ifdef CONFIG_DEBUG_BUGVERBOSE - dump_stack(); + if (!oops_in_progress) + dump_stack(); #endif /* -- 1.7.4.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists