From: Hari Vyas Date: Tue, 7 Aug 2018 11:03:48 +0000 (+0530) Subject: arm64: fix for bad_mode() handler to always result in panic X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=e4ba15debcfd27f60d43da940a58108783bff2a6;p=linux.git 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 Signed-off-by: Will Deacon Signed-off-by: Catalin Marinas --- diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c index 539b470f95262..ce29973b9bfe9 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"); }