Date: Mon, 18 Apr 2016 12:07:31 +0100
From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [parallel lookups machinery, part 2] 96352435af:
 kernel BUG at mm/slab.c:2599!
Message-ID: <20160418110731.GB25498@ZenIV.linux.org.uk>
References: <87k2jvg1yc.fsf@yhuang-dev.intel.com>
 <20160418015521.GZ25498@ZenIV.linux.org.uk>
 <87mvorvfbu.fsf@yhuang-dev.intel.com>
 <20160418021504.GA25498@ZenIV.linux.org.uk>
 <878u0bqtjk.fsf@yhuang-dev.intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <878u0bqtjk.fsf@yhuang-dev.intel.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 511
Lines: 13

On Mon, Apr 18, 2016 at 03:12:47PM +0800, Huang, Ying wrote:

> That is, there is same issue for T1, but no such issue for T2.
> 
> > How reproducible it is and how certain you are that it's not there on
> > the parent commit?
> 
> The result is quite stable for tens tests for parents and the first bad
> commit.

Nuts...  Try vfs.git#T3, please - the only way this could cause memory
corruption, AFAICS, is some really weird caller of d_add() or d_splice_alias(),
passing it a dentry with bogus ->d_parent...