[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFz9d70DCixqNdmit=OHmUi3kB9p14TDVyEvO_yRZ=2FTg@mail.gmail.com>
Date: Fri, 8 Mar 2013 20:31:48 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Dave Jones <davej@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Al Viro <viro@...iv.linux.org.uk>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: BUG_ON(nd->inode != parent->d_inode);
On Fri, Mar 8, 2013 at 7:50 PM, Dave Jones <davej@...hat.com> wrote:
> > >
> > > I have a feeling there were some sysfs ones that may still be unfixed.
>
> I was right..
>
> [ 425.836722] general protection fault: 0000 [#1] PREEMPT SMP
You forgot to enable DEBUG_PAGE_ALLOC again, but I don't think it much
matters. It's another slab free poison thing.
The faulting instruction is
mov 0x28(%rbx),%ecx
with %rbx having the value 6b6b6b6b6b6b6b6b.
> [ 425.847859] RIP: 0010:[<ffffffff8123f657>] [<ffffffff8123f657>] sysfs_find_dirent+0x47/0xf0
That seems to be
if (hash != sd->s_hash)
from sysfs_name_compare() that has been inlined into
sysfs_find_dirent(). And where "sd" is the corrupted value. If I read
things right.
So it looks like the sysfs rbtree is corrupted or something. Adding
Greg to the cc.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists