summaryrefslogtreecommitdiffstats
path: root/arch/x86
diff options
context:
space:
mode:
authorAndy Lutomirski <luto@kernel.org>2019-11-25 22:37:44 -0800
committerIngo Molnar <mingo@kernel.org>2019-11-26 22:00:12 +0100
commit0337b7ebfcb8efb4ea0a9f2b2f284217a1c0e62d (patch)
tree233be729a84456024ace6f13f1b6d7102092d61c /arch/x86
parent7d8d8cfdee9a7bd6f9682f253fa98efdd8048a9e (diff)
downloadlinux-0337b7ebfcb8efb4ea0a9f2b2f284217a1c0e62d.tar.bz2
x86/traps: die() instead of panicking on a double fault
A double fault has a decent chance of being recoverable by killing the offending thread. Use die() so that we at least try to recover. Signed-off-by: Andy Lutomirski <luto@kernel.org> Cc: Borislav Petkov <bp@alien8.de> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'arch/x86')
-rw-r--r--arch/x86/kernel/traps.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
index a9b16c3a933d..05da6b5b167b 100644
--- a/arch/x86/kernel/traps.c
+++ b/arch/x86/kernel/traps.c
@@ -427,7 +427,7 @@ dotraplinkage void do_double_fault(struct pt_regs *regs, long error_code, unsign
#endif
pr_emerg("PANIC: double fault, error_code: 0x%lx\n", error_code);
- show_regs(regs);
+ die("double fault", regs, error_code);
panic("Machine halted.");
}
#endif