From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Steven Rostedt <rostedt@goodmis.org>,
Dave Jones <davej@redhat.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Nicolas Pitre <nico@linaro.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: lockdep splat in CPU hotplug
Date: Wed, 22 Oct 2014 09:54:33 -0700 [thread overview]
Message-ID: <20141022165433.GA22874@linux.vnet.ibm.com> (raw)
In-Reply-To: <20141022143837.GW4977@linux.vnet.ibm.com>
On Wed, Oct 22, 2014 at 07:38:37AM -0700, Paul E. McKenney wrote:
> On Wed, Oct 22, 2014 at 11:53:49AM +0200, Jiri Kosina wrote:
> > On Tue, 21 Oct 2014, Jiri Kosina wrote:
> >
> > > Hi,
> > >
> > > I am seeing the lockdep report below when resuming from suspend-to-disk
> > > with current Linus' tree (c2661b80609).
> > >
> > > The reason for CCing Ingo and Peter is that I can't make any sense of one
> > > of the stacktraces lockdep is providing.
> > >
> > > Please have a look at the very first stacktrace in the dump, where lockdep
> > > is trying to explain where cpu_hotplug.lock#2 has been acquired. It seems
> > > to imply that cpuidle_pause() is taking cpu_hotplug.lock, but that's not
> > > the case at all.
> > >
> > > What am I missing?
> >
> > Okay, reverting 442bf3aaf55a ("sched: Let the scheduler see CPU idle
> > states") and followup 83a0a96a5f26 ("sched/fair: Leverage the idle state
> > info when choosing the "idlest" cpu") which depends on it makes the splat
> > go away.
> >
> > Just for the sake of testing the hypothesis, I did just the minimal change
> > below on top of current Linus' tree, and it also makes the splat go away
> > (of course it's totally incorrect thing to do by itself alone):
> >
> > diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
> > index 125150d..d31e04c 100644
> > --- a/drivers/cpuidle/cpuidle.c
> > +++ b/drivers/cpuidle/cpuidle.c
> > @@ -225,12 +225,6 @@ void cpuidle_uninstall_idle_handler(void)
> > initialized = 0;
> > wake_up_all_idle_cpus();
> > }
> > -
> > - /*
> > - * Make sure external observers (such as the scheduler)
> > - * are done looking at pointed idle states.
> > - */
> > - synchronize_rcu();
> > }
> >
> > /**
> >
> > So indeed 442bf3aaf55a is guilty.
> >
> > Paul was stating yesterday that it can't be the try_get_online_cpus() in
> > synchronize_sched_expedited(), as it's doing only trylock. There are
> > however more places where synchronize_sched_expedited() is acquiring
> > cpu_hotplug.lock unconditionally by calling put_online_cpus(), so the race
> > seems real.
>
> Gah! So I only half-eliminated the deadlock between
> synchronize_sched_expedited() and CPU hotplug. Back to the drawing
> board...
Please see below for an untested alleged fix.
Thanx, Paul
------------------------------------------------------------------------
diff --git a/kernel/cpu.c b/kernel/cpu.c
index 356450f09c1f..8589b94b005a 100644
--- a/kernel/cpu.c
+++ b/kernel/cpu.c
@@ -64,6 +64,8 @@ static struct {
* an ongoing cpu hotplug operation.
*/
int refcount;
+ /* And allows lockless put_online_cpus(). */
+ atomic_t puts_pending;
#ifdef CONFIG_DEBUG_LOCK_ALLOC
struct lockdep_map dep_map;
@@ -113,7 +115,10 @@ void put_online_cpus(void)
{
if (cpu_hotplug.active_writer == current)
return;
- mutex_lock(&cpu_hotplug.lock);
+ if (!mutex_trylock(&cpu_hotplug.lock)) {
+ atomic_inc(&cpu_hotplug.puts_pending);
+ return;
+ }
if (WARN_ON(!cpu_hotplug.refcount))
cpu_hotplug.refcount++; /* try to fix things up */
@@ -155,6 +160,12 @@ void cpu_hotplug_begin(void)
cpuhp_lock_acquire();
for (;;) {
mutex_lock(&cpu_hotplug.lock);
+ if (atomic_read(&cpu_hotplug.puts_pending)) {
+ int delta;
+
+ delta = atomic_xchg(&cpu_hotplug.puts_pending, 0);
+ cpu_hotplug.refcount -= delta;
+ }
if (likely(!cpu_hotplug.refcount))
break;
__set_current_state(TASK_UNINTERRUPTIBLE);
next prev parent reply other threads:[~2014-10-22 16:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 11:09 lockdep splat in CPU hotplug Jiri Kosina
2014-10-21 14:58 ` Steven Rostedt
2014-10-21 15:04 ` Jiri Kosina
2014-10-22 18:37 ` Steven Rostedt
2014-10-22 18:40 ` Jiri Kosina
2014-10-22 18:46 ` Borislav Petkov
2014-10-21 15:10 ` Dave Jones
2014-10-21 15:21 ` Jiri Kosina
2014-10-21 16:00 ` Paul E. McKenney
2014-10-21 16:04 ` Jiri Kosina
2014-10-21 16:23 ` Paul E. McKenney
2014-10-22 9:53 ` Jiri Kosina
2014-10-22 11:39 ` Jiri Kosina
2014-10-22 14:28 ` Daniel Lezcano
2014-10-22 14:36 ` Jiri Kosina
2014-10-22 14:45 ` Daniel Lezcano
2014-10-22 14:38 ` Paul E. McKenney
2014-10-22 16:54 ` Paul E. McKenney [this message]
2014-10-22 18:57 ` Paul E. McKenney
2014-10-22 20:57 ` Jiri Kosina
2014-10-22 21:09 ` Paul E. McKenney
2014-10-23 8:11 ` Borislav Petkov
2014-10-23 14:56 ` Paul E. McKenney
2014-10-22 16:59 ` Steven Rostedt
2014-10-22 17:26 ` Jiri Kosina
2014-10-24 14:33 ` Peter Zijlstra
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=20141022165433.GA22874@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=daniel.lezcano@linaro.org \
--cc=davej@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nico@linaro.org \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=rostedt@goodmis.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.