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

Open Source and information security mailing list archives

Message-ID: <87mvorvfbu.fsf@yhuang-dev.intel.com>
Date:	Mon, 18 Apr 2016 10:08:37 +0800
From:	"Huang\, Ying" <ying.huang@...el.com>
To:	Al Viro <viro@...IV.linux.org.uk>
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!

Al Viro <viro@...IV.linux.org.uk> writes:

> On Mon, Apr 18, 2016 at 09:06:35AM +0800, kernel test robot wrote:
>> FYI, we noticed the below changes on
>> 
>> https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git testing.lookups
>> commit 96352435afd792d713ec91e2d5693bdcf40a6b03 ("parallel lookups machinery, part 2")
>
> Very odd.  All stores in that commit are to ->d_parent->d_inode->i_dir_seq
> of in-lookup dentries.  And if ->d_parent in those gets buggered, we were
> really deep in trouble.  Could you try to reproduce that without __d_move()
> or __d_add() parts and see which one ends up triggering that crap?

Could you provide a debug branch in your tree for that?

Best Regards,
Huang, Ying

> Note that we don't *use* ->i_dir_seq yet...
> _______________________________________________
> LKP mailing list
> LKP@...ts.01.org
> https://lists.01.org/mailman/listinfo/lkp

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