From: David Howells <dhowells@redhat.com>
To: Patrick Mochel <mochel@osdl.org>, viro@math.psu.edu
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.64 sysfs bug
Date: Fri, 07 Mar 2003 11:05:40 +0000 [thread overview]
Message-ID: <5557.1047035140@warthog.cambridge.redhat.com> (raw)
Hi, I seem to be getting tripping a bug somewhere with my filesystem now that
I'm using it with 2.5.64 (no problems of this nature occurred with
2.5.63). The problem occurs during rmmod (I don't need to actually mount
anything):
[root@host135 root]# insmod /tmp/cachefs.ko
[root@host135 root]# rmmod -f cachefs
[root@host135 root]# insmod /tmp/cachefs.ko
[root@host135 root]# rmmod -f cachefs
Segmentation fault
[root@host135 root]#
I see this appearing on the console:
[insmod] ==> cachefs_init()
CacheFS: Started kcachefs_jnld 1161
[insmod] ==> cachefs_fs_init()
[insmod] <== cachefs_fs_init() = 0
[insmod] <== cachefs_init()
[rmmod ] ==> cachefs_exit()
[rmmod ] ==> cachefs_fs_exit()
[rmmod ] <== cachefs_fs_exit()
[kujnld] <== kcachefs_jnld()
[rmmod ] <== cachefs_exit() = 0
[insmod] ==> cachefs_init()
CacheFS: Started kcachefs_jnld 1164
[insmod] ==> cachefs_fs_init()
[insmod] <== cachefs_fs_init() = 0
[insmod] <== cachefs_init()
[rmmod ] ==> cachefs_exit()
[rmmod ] ==> cachefs_fs_exit()
------------[ cut here ]------------
kernel BUG at include/linux/dcache.h:266!
invalid operand: 0000
CPU: 0
EIP: 0060:[<c019016c>] Not tainted
EFLAGS: 00010246
EIP is at sysfs_remove_dir+0x1c/0x14e
eax: 00000000 ebx: c886b494 ecx: c0331bc4 edx: c886b480
esi: c6a7abcc edi: c69be000 ebp: c69be000 esp: c69bff00
ds: 007b es: 007b ss: 0068
Process rmmod (pid: 1165, threadinfo=c69be000 task=c6e40ca0)
Stack: 00001b05 00001b27 fffffffd c886b494 c886b480 c69be000 c69be000 c01faa13
c886b494 c886b494 c01faa43 c886b494 00000000 c017516b c886b494 c69be000
00000000 c886661d c886b480 c6e40f96 c88669b4 c886b560 c88665a8 c8867500
Call Trace:
[<c886b494>] cachefs_fs_type+0x14/0x80 [cachefs]
[<c886b480>] cachefs_fs_type+0x0/0x80 [cachefs]
[<c01faa13>] kobject_del+0x13/0x30
[<c886b494>] cachefs_fs_type+0x14/0x80 [cachefs]
[<c886b494>] cachefs_fs_type+0x14/0x80 [cachefs]
[<c01faa43>] kobject_unregister+0x13/0x30
[<c886b494>] cachefs_fs_type+0x14/0x80 [cachefs]
[<c017516b>] unregister_filesystem+0x3b/0x40
[<c886b494>] cachefs_fs_type+0x14/0x80 [cachefs]
[<c886661d>] cachefs_fs_exit+0x4d/0xb0 [cachefs]
[<c886b480>] cachefs_fs_type+0x0/0x80 [cachefs]
[<c88669b4>] __func__.1+0x0/0x10 [cachefs]
[<c886b560>] +0x0/0x120 [cachefs]
[<c88665a8>] cachefs_exit+0x28/0x50 [cachefs]
[<c8867500>] +0xa80/0x1511 [cachefs]
[<c013538e>] sys_delete_module+0x1ae/0x1e0
[<c013538e>] sys_delete_module+0x1ae/0x1e0
[<c886b560>] +0x0/0x120 [cachefs]
[<c014804e>] sys_brk+0xfe/0x130
[<c0117380>] do_page_fault+0x0/0x47f
[<c0109ac3>] syscall_call+0x7/0xb
Code: 0f 0b 0a 01 8b 37 2e c0 f0 ff 06 83 4e 04 08 85 f6 0f 84 13
The cachefs_fs_exit() function is:
void __exit cachefs_fs_exit(void)
{
kenter("");
unregister_filesystem(&cachefs_fs_type);
/* destroy our private inode cache */
kmem_cache_destroy(cachefs_inode_cachep);
kleave("");
} /* end cachefs_fs_exit() */
The function causing the bug report is:
[include/linux/dcache.h]
static __inline__ struct dentry * dget(struct dentry *dentry)
{
if (dentry) {
if (!atomic_read(&dentry->d_count))
BUG();
atomic_inc(&dentry->d_count);
dentry->d_vfs_flags |= DCACHE_REFERENCED;
}
return dentry;
}
David
next reply other threads:[~2003-03-07 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 11:05 David Howells [this message]
2003-03-07 15:49 ` 2.5.64 sysfs bug Patrick Mochel
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=5557.1047035140@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=viro@math.psu.edu \
/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