From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Fix deadlock scenario with smp_send_stop()
Date: Wed, 24 Jul 2013 13:29:00 -0700 [thread overview]
Message-ID: <51F0390C.7090501@codeaurora.org> (raw)
In-Reply-To: <20130724202148.GA24642@n2100.arm.linux.org.uk>
On 07/24/13 13:21, Russell King - ARM Linux wrote:
> On Wed, Jul 24, 2013 at 11:56:18AM -0700, Stephen Boyd wrote:
>> On 07/09, Stephen Boyd wrote:
>>> 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.
>>>
>>> Reported-by: Sundarajan Srinivasan <sundaraj@codeaurora.com>
>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>> ---
>>>
>>> Resending this patch now that the context has changed.
>> Ping? Shall I put this in the patch tracker?
> Well, looking at x86, they use local_irq_disable() before sending the
> stop, so I think we should do the same for cross-arch consistency.
Fair enough. I'll send v2 with that.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@codeaurora.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: Fix deadlock scenario with smp_send_stop()
Date: Wed, 24 Jul 2013 13:29:00 -0700 [thread overview]
Message-ID: <51F0390C.7090501@codeaurora.org> (raw)
In-Reply-To: <20130724202148.GA24642@n2100.arm.linux.org.uk>
On 07/24/13 13:21, Russell King - ARM Linux wrote:
> On Wed, Jul 24, 2013 at 11:56:18AM -0700, Stephen Boyd wrote:
>> On 07/09, Stephen Boyd wrote:
>>> 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.
>>>
>>> Reported-by: Sundarajan Srinivasan <sundaraj@codeaurora.com>
>>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>>> ---
>>>
>>> Resending this patch now that the context has changed.
>> Ping? Shall I put this in the patch tracker?
> Well, looking at x86, they use local_irq_disable() before sending the
> stop, so I think we should do the same for cross-arch consistency.
Fair enough. I'll send v2 with that.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-07-24 20:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 15:36 [PATCH] ARM: Fix deadlock scenario with smp_send_stop() Stephen Boyd
2013-07-09 15:36 ` Stephen Boyd
2013-07-24 18:56 ` Stephen Boyd
2013-07-24 18:56 ` Stephen Boyd
2013-07-24 20:21 ` Russell King - ARM Linux
2013-07-24 20:21 ` Russell King - ARM Linux
2013-07-24 20:29 ` Stephen Boyd [this message]
2013-07-24 20:29 ` Stephen Boyd
2013-07-24 20:36 ` [PATCH v2] " Stephen Boyd
2013-07-24 20:36 ` Stephen Boyd
2013-07-30 22:12 ` Stephen Boyd
2013-07-30 22:12 ` Stephen Boyd
-- strict thread matches above, loose matches on Subject: below --
2012-09-05 21:01 [PATCH] " Stephen Boyd
2012-09-05 21:01 ` Stephen Boyd
2012-09-11 18:08 ` Stephen Boyd
2012-09-11 18:08 ` Stephen Boyd
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=51F0390C.7090501@codeaurora.org \
--to=sboyd@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.