aboutsummaryrefslogtreecommitdiffstats
path: root/arch/arm64
diff options
context:
space:
mode:
authorHari Vyas <hari.vyas@broadcom.com>2018-08-07 16:33:48 +0530
committerCatalin Marinas <catalin.marinas@arm.com>2018-09-14 17:46:25 +0100
commite4ba15debcfd27f60d43da940a58108783bff2a6 (patch)
tree2a01ebdec3611ac984827b78dde854ee8ec83f53 /arch/arm64
parentarm64: force_signal_inject: WARN if called from kernel context (diff)
downloadlinux-dev-e4ba15debcfd27f60d43da940a58108783bff2a6.tar.xz
linux-dev-e4ba15debcfd27f60d43da940a58108783bff2a6.zip
arm64: fix for bad_mode() handler to always result in panic
The bad_mode() handler is called if we encounter an uunknown exception, with the expectation that the subsequent call to panic() will halt the system. Unfortunately, if the exception calling bad_mode() is taken from EL0, then the call to die() can end up killing the current user task and calling schedule() instead of falling through to panic(). Remove the die() call altogether, since we really want to bring down the machine in this "impossible" case. Signed-off-by: Hari Vyas <hari.vyas@broadcom.com> Signed-off-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'arch/arm64')
-rw-r--r--arch/arm64/kernel/traps.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
index 539b470f9526..ce29973b9bfe 100644
--- a/arch/arm64/kernel/traps.c
+++ b/arch/arm64/kernel/traps.c
@@ -606,7 +606,6 @@ asmlinkage void bad_mode(struct pt_regs *regs, int reason, unsigned int esr)
handler[reason], smp_processor_id(), esr,
esr_get_class_string(esr));
- die("Oops - bad mode", regs, 0);
local_daif_mask();
panic("bad mode");
}