[Xen-changelog] [xen stable-4.4] xen/arm: Panic when we receive an unexpected trap

[patchbot@xxxxxxx]

commit 0424674f3fa98b7792c838725fbf5623258698b1
Author:     Julien Grall <julien.grall@xxxxxxxxxx>
AuthorDate: Tue Jun 17 21:44:28 2014 +0100
Commit:     Ian Campbell <ian.campbell@xxxxxxxxxx>
CommitDate: Wed Jul 2 10:37:00 2014 +0100

    xen/arm: Panic when we receive an unexpected trap
    
    The current implementation of do_unexpected_trap make Xen spin forever
    on the current physical CPU. This may lead to stall guests VCPU and print
    unhelpful message (RCU stall...).
    
    Usually when Xen receives an unexpected trap, it means that something goes
    wrong either in the hypervisor or in the CPU. In this case we should
    directly panic to also stop the other CPUs.
    
    Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx>
    Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx>
    (cherry picked from commit 4f5ab681d208993f94553203f4be323b3c929070)
---
 xen/arch/arm/traps.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c
index 377f18f..1498ea0 100644
--- a/xen/arch/arm/traps.c
+++ b/xen/arch/arm/traps.c
@@ -999,7 +999,7 @@ void do_unexpected_trap(const char *msg, struct 
cpu_user_regs *regs)
 {
     printk("CPU%d: Unexpected Trap: %s\n", smp_processor_id(), msg);
     show_execution_state(regs);
-    while(1);
+    panic("CPU%d: Unexpected Trap: %s\n", smp_processor_id(), msg);
 }
 
 typedef register_t (*arm_hypercall_fn_t)(
--
generated by git-patchbot for /home/xen/git/xen.git#stable-4.4

_______________________________________________
Xen-changelog mailing list
Xen-changelog@xxxxxxxxxxxxx
http://lists.xensource.com/xen-changelog