From: Valdis.Kletnieks@vt.edu
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Joel Becker <joel.becker@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: 2.6.37-next - kernel BUG at fs/dcache.c:1363
Date: Wed, 05 Jan 2011 12:15:41 -0500 [thread overview]
Message-ID: <8679.1294247741@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Saw this crash on a linux-next pulled yesterday at 2PM EST, kernel dies very
early (looks like first time it touches configfs for anything - trying to boot
with netconsole enabled caused it to die even faster). I can bisect this if
it doesn't immediately ring a bell...
It dies here:
void d_set_d_op(struct dentry *dentry, const struct dentry_operations *op)
{
BUG_ON(dentry->d_op);
Am guessing configfs passed in a dentry that wasn't filled in enough.
(hand-transcribed from a crappy cellphone pic)
kernel BUG at fs/dcache.c:1363
invalid opcode: 0000 [#1] PREEMT SMP
last sysfs file:
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.37-rc8-next-2011 (edge of pic)
...
configfs_attach_item.clone.14+0x11d/0x254
configfs_attach_group.clone.15+0x1c/0x196
? _raw_spinlock_unlock+0x5c/0x69
configfs_register_subsystem_0xce/0x144
? init_netconsole+0x0/0x21f
init_netconsole+0x10d/0x21f
? init_netconsole+0x0/0x21f
do_one_initcall+0x52/0x12f
kernel_init+0x162/0x1e7
kernel_thread_helper+0x4/0x10
? finish_task_switch_0x3f/0xe3
? restore_args+0x0/0x30
? kernel_init+0x0/0x1e7
? kernel_thread_helper+0x0/0x10
I d_net_d_op+0x38/0xb0
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next reply other threads:[~2011-01-05 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 17:15 Valdis.Kletnieks [this message]
2011-01-06 10:44 ` 2.6.37-next - kernel BUG at fs/dcache.c:1363 Nick Piggin
2011-01-06 13:12 ` Nick Piggin
2011-01-07 17:10 ` Valdis.Kletnieks
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=8679.1294247741@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=joel.becker@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).