From: Al Viro <viro@ZenIV.linux.org.uk>
To: lkp@lists.01.org
Subject: Re: [parallel lookups machinery, part 2] 96352435af: kernel BUG at mm/slab.c:2599!
Date: Mon, 18 Apr 2016 02:55:21 +0100 [thread overview]
Message-ID: <20160418015521.GZ25498@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87k2jvg1yc.fsf@yhuang-dev.intel.com>
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
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...
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp] [parallel lookups machinery, part 2] 96352435af: kernel BUG at mm/slab.c:2599!
Date: Mon, 18 Apr 2016 02:55:21 +0100 [thread overview]
Message-ID: <20160418015521.GZ25498@ZenIV.linux.org.uk> (raw)
In-Reply-To: <87k2jvg1yc.fsf@yhuang-dev.intel.com>
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...
next prev parent reply other threads:[~2016-04-18 1:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 1:06 [parallel lookups machinery, part 2] 96352435af: kernel BUG at mm/slab.c:2599! kernel test robot
2016-04-18 1:06 ` [lkp] " kernel test robot
2016-04-18 1:55 ` Al Viro [this message]
2016-04-18 1:55 ` Al Viro
2016-04-18 2:08 ` Huang, Ying
2016-04-18 2:08 ` [LKP] [lkp] " Huang, Ying
2016-04-18 2:15 ` Al Viro
2016-04-18 2:15 ` [LKP] [lkp] " Al Viro
2016-04-18 7:12 ` Huang, Ying
2016-04-18 7:12 ` [LKP] [lkp] " Huang, Ying
2016-04-18 11:07 ` Al Viro
2016-04-18 11:07 ` [LKP] [lkp] " Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160418015521.GZ25498@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=lkp@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.