From: Peter Zijlstra <peterz@infradead.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Mike Galbraith <efault@gmx.de>,
Matt Fleming <matt@codeblueprint.co.uk>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Michal Hocko <mhocko@suse.com>
Subject: Re: cpu stopper threads and load balancing leads to deadlock
Date: Thu, 3 May 2018 16:52:21 +0200 [thread overview]
Message-ID: <20180503145221.GE12217@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180503143941.GH26088@linux.vnet.ibm.com>
On Thu, May 03, 2018 at 07:39:41AM -0700, Paul E. McKenney wrote:
> Huh.
>
> No, RCU_NONIDLE() only works for idle, not for offline.
Oh bummer..
> Maybe... Let me take a look. There must be some way to mark a
> specific lock acquisition and release as being lockdep-invisible...
But I suspect it flags a real issue. Shutting it up isn't the issue as
such. There could be a concurrent sched domain rebuild while we do this
setup, and if we free that domain while we're looking at it, bad things
happen.
... I wonder what brought this failure to pass now. This code has been
like this a for a long time.
next prev parent reply other threads:[~2018-05-03 14:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 14:21 cpu stopper threads and load balancing leads to deadlock Matt Fleming
2018-04-18 5:47 ` Mike Galbraith
2018-04-19 5:38 ` Mike Galbraith
2018-04-20 9:50 ` Peter Zijlstra
2018-04-24 13:33 ` Matt Fleming
2018-05-03 12:12 ` Mike Galbraith
2018-05-03 12:28 ` Peter Zijlstra
2018-05-03 12:40 ` Mike Galbraith
2018-05-03 12:49 ` Peter Zijlstra
2018-05-03 13:32 ` Mike Galbraith
2018-05-03 13:56 ` Peter Zijlstra
2018-05-03 14:16 ` Mike Galbraith
2018-05-03 14:44 ` Peter Zijlstra
2018-05-03 16:12 ` Paul E. McKenney
2018-05-03 16:45 ` Peter Zijlstra
2018-05-03 17:18 ` Paul E. McKenney
2018-05-03 17:54 ` Peter Zijlstra
2018-05-03 18:24 ` Paul E. McKenney
2018-05-04 3:38 ` Mike Galbraith
2018-05-15 4:30 ` Mike Galbraith
2018-05-17 14:03 ` Paul E. McKenney
2018-05-17 14:10 ` Mike Galbraith
2018-05-17 14:23 ` Peter Zijlstra
2018-05-17 14:56 ` Paul E. McKenney
2018-05-22 17:05 ` Paul E. McKenney
2018-05-03 14:39 ` Paul E. McKenney
2018-05-03 14:52 ` Peter Zijlstra [this message]
2018-05-03 9:24 ` [tip:sched/urgent] stop_machine, sched: Fix migrate_swap() vs. active_balance() deadlock tip-bot for 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=20180503145221.GE12217@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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.