From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1754481AbbBLAmR (ORCPT <rfc822;w@1wt.eu>);
	Wed, 11 Feb 2015 19:42:17 -0500
Received: from e32.co.us.ibm.com ([32.97.110.150]:54365 "EHLO
	e32.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752572AbbBLAmP (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 11 Feb 2015 19:42:15 -0500
Date: Wed, 11 Feb 2015 16:42:10 -0800
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>, Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>,
        LKML <linux-kernel@vger.kernel.org>,
        "davej@codemonkey.org.uk >> Dave Jones" <davej@codemonkey.org.uk>
Subject: Re: rcu, sched: WARNING: CPU: 30 PID: 23771 at
 kernel/rcu/tree_plugin.h:337 rcu_read_unlock_special+0x369/0x550()
Message-ID: <20150212004209.GP4166@linux.vnet.ibm.com>
Reply-To: paulmck@linux.vnet.ibm.com
References: <20150123093644.GA11175@linux.vnet.ibm.com>
 <54C300DD.9070608@cn.fujitsu.com>
 <20150124211834.GD9719@linux.vnet.ibm.com>
 <54C5A184.20105@cn.fujitsu.com>
 <20150127220329.GF19109@linux.vnet.ibm.com>
 <54C80C55.2070908@oracle.com>
 <20150127231659.GG19109@linux.vnet.ibm.com>
 <54CBE20C.9010008@oracle.com>
 <20150130203354.GT19109@linux.vnet.ibm.com>
 <54DBE308.7070208@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54DBE308.7070208@oracle.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 15021200-0005-0000-0000-000008BB4A06
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Feb 11, 2015 at 06:17:28PM -0500, Sasha Levin wrote:
> On 01/30/2015 03:33 PM, Paul E. McKenney wrote:
> >>> Either way, may I have your Tested-by?
> >> > 
> >> > Yup, I haven't seen it so far.
> > Thank you!
> 
> I'm still seeing this issue in -next, and I see that that commit wasn't
> applied yet.
> 
> Anything it's waiting on?

Me to get my act together and move it from my for-v3.21 bucket into my
for-v3.20 bucket.  I have rebased and have started testing, should hit
-next soon.  If all goes well, I will send a pull request.

							Thanx, Paul