All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: 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, 03 May 2018 14:40:21 +0200	[thread overview]
Message-ID: <1525351221.9956.4.camel@gmx.de> (raw)
In-Reply-To: <20180503122808.GZ12217@hirez.programming.kicks-ass.net>

On Thu, 2018-05-03 at 14:28 +0200, Peter Zijlstra wrote:
> 
> Hurm.. I don't see how this is 'new'. We moved the wakeup out from under
> stopper lock, but that should not affect the RCU state.

No, not new, just an additional woes from same spot.

	-Mike

  reply	other threads:[~2018-05-03 12:40 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 [this message]
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
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=1525351221.9956.4.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=mhocko@suse.com \
    --cc=mingo@kernel.org \
    --cc=peterz@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.