linux-kernel - Re: [LKP] [lkp] [parallel lookups machinery, part 2] 96352435af: kernel BUG at mm/slab.c:2599!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 18 Apr 2016 12:07:31 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	"Huang, Ying" <ying.huang@...el.com>
Cc:	lkp@...org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [LKP] [lkp] [parallel lookups machinery, part 2] 96352435af:
 kernel BUG at mm/slab.c:2599!

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...