linux-kernel - Re: [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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160418015521.GZ25498@ZenIV.linux.org.uk>
Date:	Mon, 18 Apr 2016 02:55:21 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	kernel test robot <ying.huang@...ux.intel.com>
Cc:	lkp@...org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [lkp] [parallel lookups machinery, part 2] 96352435af: kernel
 BUG at mm/slab.c:2599!

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?

Note that we don't *use* ->i_dir_seq yet...