From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] VFS - the first pile
Date: Wed, 16 Mar 2011 09:05:04 -0400 [thread overview]
Message-ID: <20110316130504.GA30866@infradead.org> (raw)
In-Reply-To: <20110315213248.GL22723@ZenIV.linux.org.uk>
This blows up on xfstests 005 for me:
005 0s ...
[ 25.075985] ------------[ cut here ]------------
[ 25.076043] kernel BUG at /home/hch/work/linux-2.6/fs/dcache.c:440!
[ 25.076043] invalid opcode: 0000 [#1] SMP
[ 25.076043] last sysfs file: /sys/devices/pci0000:00/0000:00:05.0/virtio1/block/vdb/removable
[ 25.076043] Modules linked in:
[ 25.076043]
[ 25.076043] Pid: 6263, comm: touch Not tainted 2.6.38+ #77 Bochs Bochs
[ 25.076043] EIP: 0060:[<c021d36e>] EFLAGS: 00010246 CPU: 0
[ 25.076043] EIP is at dput+0x22e/0x240
[ 25.076043] EAX: 00000000 EBX: f54b9f14 ECX: 00000000 EDX: 00005959
[ 25.076043] ESI: ffffffd8 EDI: ffffffd8 EBP: f5361e84 ESP: f5361e68
[ 25.076043] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 25.076043] Process touch (pid: 6263, ti=f5360000 task=f59c23f0 task.ti=f5360000)
[ 25.076043] Stack:
[ 25.076043] 0000000c f54b9f14 f5361eec f54b9f60 f5361eb8 ffffffd8 ffffffd8 f5361e90
[ 25.076043] c02129ce f5361eec f5361ed8 c0215702 f644d000 f5361ec8 f5361f78 f644d000
[ 25.076043] f59c23f0 f5361f00 f59c23f0 c04c0aa0 f5a18180 f54b9f14 f5a18180 f54b9f14
[ 25.076043] Call Trace:
[ 25.076043] [<c02129ce>] path_put+0xe/0x20
[ 25.076043] [<c0215702>] path_openat+0x1d2/0x310
[ 25.076043] [<c04c0aa0>] ? xfs_vn_put_link+0x0/0x20
[ 25.076043] [<c0215920>] do_filp_open+0x30/0x80
[ 25.076043] [<c02205cc>] ? alloc_fd+0x6c/0xf0
[ 25.076043] [<c0213171>] ? getname_flags+0x61/0xe0
[ 25.076043] [<c020915b>] do_sys_open+0xeb/0x1c0
[ 25.076043] [<c0209299>] sys_open+0x29/0x40
[ 25.076043] [<c08f62b9>] syscall_call+0x7/0xb
[ 25.076043] Code: 89 72 04 89 53 60 8d 50 7c 89 53 64 89 70 7c 8b 43 54 83 80 84 00 00 00 01 83 05 a8 32 c4 c0 01 fe 05 00 4c c3 c0 e9 8b fe ff ff <0f> 0b eb fe 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 55 89 e5
next prev parent reply other threads:[~2011-03-16 13:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 21:32 [git pull] VFS - the first pile Al Viro
2011-03-15 22:02 ` Sam Ravnborg
2011-03-15 22:18 ` Al Viro
2011-03-15 22:47 ` Linus Torvalds
2011-03-15 23:02 ` Al Viro
2011-03-16 6:19 ` Dave Chinner
2011-03-16 6:51 ` Al Viro
2011-03-16 7:21 ` Al Viro
2011-03-16 11:46 ` Theodore Tso
2011-03-16 13:07 ` Christoph Hellwig
2011-03-16 13:15 ` Al Viro
2011-03-16 13:18 ` Christoph Hellwig
2011-03-16 13:05 ` Christoph Hellwig [this message]
2011-03-16 13:10 ` Christoph Hellwig
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=20110316130504.GA30866@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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