From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Fix deadlock scenario with smp_send_stop()
Date: Wed, 24 Jul 2013 21:21:48 +0100 [thread overview]
Message-ID: <20130724202148.GA24642@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130724185618.GD27761@codeaurora.org>
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.
next prev parent reply other threads:[~2013-07-24 20:21 UTC|newest]
Thread overview: 8+ 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-24 18:56 ` Stephen Boyd
2013-07-24 20:21 ` Russell King - ARM Linux [this message]
2013-07-24 20:29 ` Stephen Boyd
2013-07-24 20:36 ` [PATCH v2] " 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-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=20130724202148.GA24642@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).