arm64: Fix deadlock scenario with smp_send_stop()
authorArun KS <arunks.linux@gmail.com>
Wed, 7 May 2014 01:41:23 +0000 (02:41 +0100)
committerHuang, Tao <huangtao@rock-chips.com>
Fri, 27 Mar 2015 06:28:08 +0000 (14:28 +0800)
commita3017b51a38fd20da33f16ae33fdf33c3f2a3e43
tree24d35c23283332e8487725cd5a04a019ff132e33
parent363aaed735c13f4d944c8cd2243e2c66895bd316
arm64: Fix deadlock scenario with smp_send_stop()

If one process calls sys_reboot and that process then stops other
CPUs while those CPUs are within a spin_lock() region we can
potentially encounter a deadlock scenario like below.

CPU 0                   CPU 1
-----                   -----
                        spin_lock(my_lock)
smp_send_stop()
 <send IPI>             handle_IPI()
                         disable_preemption/irqs
                          while(1);
 <PREEMPT>
spin_lock(my_lock) <--- Waits forever

We shouldn't attempt to run any other tasks after we send a stop
IPI to a CPU so disable preemption so that this task runs to
completion. We use local_irq_disable() here for cross-arch
consistency with x86.

Based-on-work-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Arun KS <getarunks@gmail.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
(cherry picked from commit b9acc49ee9464f8f8232a790045d057eb158e869)

Conflicts:
arch/arm64/kernel/process.c
arch/arm64/kernel/process.c