linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lan Tianyu <tianyu.lan@intel.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
	laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com,
	bobby.prani@gmail.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH RFC tip/core/rcu] Eliminate deadlock between CPU hotplug and expedited grace periods
Date: Thu, 18 Sep 2014 15:15:36 +0800	[thread overview]
Message-ID: <541A8698.9040905@intel.com> (raw)
In-Reply-To: <20140917131013.GU4723@linux.vnet.ibm.com>

On 2014年09月17日 21:10, Paul E. McKenney wrote:
> On Wed, Sep 17, 2014 at 03:11:42PM +0800, Lan Tianyu wrote:
>> On 2014年08月29日 03:47, Paul E. McKenney wrote:
>>> Currently, the expedited grace-period primitives do get_online_cpus().
>>> This greatly simplifies their implementation, but means that calls to
>>> them holding locks that are acquired by CPU-hotplug notifiers (to say
>>> nothing of calls to these primitives from CPU-hotplug notifiers) can
>>> deadlock.  But this is starting to become inconvenient:
>>> https://lkml.org/lkml/2014/8/5/754
>>>
>>> This commit avoids the deadlock and retains the simplicity by creating
>>> a try_get_online_cpus(), which returns false if the get_online_cpus()
>>> reference count could not immediately be incremented.  If a call to
>>> try_get_online_cpus() returns true, the expedited primitives operate
>>> as before.  If a call returns false, the expedited primitives fall back
>>> to normal grace-period operations.  This falling back of course results
>>> in increased grace-period latency, but only during times when CPU
>>> hotplug operations are actually in flight.  The effect should therefore
>>> be negligible during normal operation.
>>>
>>> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
>>> Cc: Josh Triplett <josh@joshtriplett.org>
>>> Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
>>> Cc: Lan Tianyu <tianyu.lan@intel.com>
>>
>> Hi Paul:
>> 	What's the status of the patch? Will you push it? Thanks.
> 
> By default, it would go into 3.19.  Do you need it earlier?

IMO, this is a dead lock bug which is hard to reproduce and the patch
should go into v3.17 and stable tree?

> 
> 							Thanx, Paul
> 


-- 
Best regards
Tianyu Lan

  reply	other threads:[~2014-09-18  7:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 19:47 [PATCH RFC tip/core/rcu] Eliminate deadlock between CPU hotplug and expedited grace periods Paul E. McKenney
2014-08-29  6:54 ` Lan Tianyu
2014-08-29 13:11   ` Paul E. McKenney
2014-09-01 11:20 ` Peter Zijlstra
2014-09-01 16:05   ` Paul E. McKenney
2014-09-01 16:17     ` Peter Zijlstra
2014-09-02 16:36       ` Paul E. McKenney
2014-09-03 11:31         ` Peter Zijlstra
2014-09-03 15:03           ` Paul E. McKenney
2014-09-03 15:28             ` Peter Zijlstra
2014-09-03 16:38               ` Paul E. McKenney
2014-09-17  7:11 ` Lan Tianyu
2014-09-17 13:10   ` Paul E. McKenney
2014-09-18  7:15     ` Lan Tianyu [this message]
2014-09-18 12:38       ` Paul E. McKenney
2014-09-18 22:55         ` Rafael J. Wysocki
2014-09-18 22:57           ` Paul E. McKenney

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=541A8698.9040905@intel.com \
    --to=tianyu.lan@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bobby.prani@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=dvhart@linux.intel.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).