From: arunks.linux@gmail.com (arunks.linux at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 2/2] arm64: Fix deadlock scenario with smp_send_stop()
Date: Wed, 7 May 2014 07:11:23 +0530 [thread overview]
Message-ID: <1399426883-13779-2-git-send-email-arunks.linux@gmail.com> (raw)
In-Reply-To: <1399426883-13779-1-git-send-email-arunks.linux@gmail.com>
From: Arun KS <arunks.linux@gmail.com>
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>
---
arch/arm64/kernel/process.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
index 2d43614..abe57e0 100644
--- a/arch/arm64/kernel/process.c
+++ b/arch/arm64/kernel/process.c
@@ -134,6 +134,7 @@ void machine_shutdown(void)
*/
void machine_halt(void)
{
+ local_irq_disable();
smp_send_stop();
while (1);
}
@@ -146,6 +147,7 @@ void machine_halt(void)
*/
void machine_power_off(void)
{
+ local_irq_disable();
smp_send_stop();
if (pm_power_off)
pm_power_off();
@@ -164,10 +166,9 @@ void machine_power_off(void)
*/
void machine_restart(char *cmd)
{
- smp_send_stop();
-
/* Disable interrupts first */
local_irq_disable();
+ smp_send_stop();
/* Now call the architecture specific reboot code. */
if (arm_pm_restart)
--
1.7.6
next prev parent reply other threads:[~2014-05-07 1:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 1:41 [PATCH v1 1/2] arm64: Fix machine_shutdown() definition arunks.linux at gmail.com
2014-05-07 1:41 ` arunks.linux at gmail.com [this message]
2014-05-07 15:43 ` Stephen Warren
2014-05-16 17:20 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1399426883-13779-2-git-send-email-arunks.linux@gmail.com \
--to=arunks.linux@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).