From: Steven Rostedt <rostedt@goodmis.org>
To: frank.rowand@am.sony.com
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org
Subject: Re: 3.0.23-rt39 BUG: scheduling while atomic, _cpu_down()
Date: Fri, 09 Mar 2012 21:03:12 -0500 [thread overview]
Message-ID: <1331344992.25686.612.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4F5AB3B6.2040705@am.sony.com>
On Fri, 2012-03-09 at 17:51 -0800, Frank Rowand wrote:
> Hi Thomas,
> (and Steve, since you've been mucking about in the hotplug code,)
>
> Yet another bit of fallout related to hotplug.
>
> This appears to affect 3.0-rt1, 3.0.23-rt29, and 3.2.9-rt17.
> (Thus probably all 3.x versions, but I haven't been masochistic
> enough to check.)
>
> If not defined CONFIG_PREEMPT_RT_FULL then
So you're saying that there's a bug with PREEMPT_RT off?
>
> - hotplug_lock() is a mutex_lock()
> - cpu_hotplug_begin() calls hotplug_lock()
> - _cpu_down() calls cpu_hotplug_begin() with preemption
> disabled (disabled by the migrate_disable())
>
> The call to cpu_hotplug_begin() is not in a preempt disabled
> region until hotplug-use-migrate-disable.patch. This patch
> moves the preempt_enable() (aka migrate_enable()) from just
> before calling cpu_hotplug_begin() to after "out_cancel:".
>
> The BUG can be triggered by:
>
> echo 0 > /sys/devices/system/cpu/cpu1/online
Note, there's a lot more wrong with hotplug in rt than this. The hotplug
code really needs a total rewrite for RT to work with it. It probably
should have a total rewrite in mainline anyway.
-- Steve
next prev parent reply other threads:[~2012-03-10 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 1:51 Frank Rowand
2012-03-10 2:03 ` Steven Rostedt [this message]
2012-03-10 2:12 ` Frank Rowand
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=1331344992.25686.612.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=frank.rowand@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®