From: Tao Ma <tm@tao.ma>
To: npiggin@gmail.com, Linux Kernel <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org, Theodore Tso <tytso@mit.edu>
Subject: 38-rc1: umount+rmmod cause ext4 error.
Date: Wed, 19 Jan 2011 14:53:36 +0800 [thread overview]
Message-ID: <4D368A70.5030103@tao.ma> (raw)
Hi Nick and Ted,
I ran some very basic test with 38-rc1 and my box run into error with
the message like:
slab error in kmem_cache_destroy(): cache `ext4_inode_cache': Can't free
all objects
Pid: 4395, comm: rmmod Not tainted 2.6.38-rc1 #1
Call Trace:
[<ffffffff820d61dc>] ? kmem_cache_destroy+0x83/0xc7
[<ffffffffa0574025>] ? destroy_inodecache+0x15/0x17 [ext4]
[<ffffffffa05923d1>] ? ext4_exit_fs+0x109/0x143 [ext4]
[<ffffffff8203d194>] ? put_online_cpus+0x56/0x58
[<ffffffff8206735a>] ? module_refcount+0x85/0x9d
[<ffffffff82067b22>] ? sys_delete_module+0x1b5/0x218
[<ffffffff82074fc3>] ? audit_syscall_entry+0x187/0x1ba
[<ffffffff82002a6b>] ? system_call_fastpath+0x16/0x1b
SLAB: cache with size 888 has lost its name
SLAB: cache with size 888 has lost its name
SLAB: cache with size 888 has lost its name
SLAB: cache with size 888 has lost its name
The reproduce process is simple:just rmmod ext4 immediately after umount
an ext4 volume.
I have done some very simple investigation and it seems that with Nick's
new ext4_i_callback, even after we do ext4_destroy_inode, it isn't
freed. So after we destroy the ext_inode_cache, and when freeing the
inode, it errors. Hope it helps. If you have any fixes, I can test it.
Regards,
Tao
next reply other threads:[~2011-01-19 6:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 6:53 Tao Ma [this message]
2011-01-26 20:28 ` 38-rc1: umount+rmmod cause ext4 error Maciej Rutecki
2011-01-26 20:28 ` Maciej Rutecki
2011-01-26 20:40 ` Eric Sandeen
2011-01-26 20:40 ` Eric Sandeen
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=4D368A70.5030103@tao.ma \
--to=tm@tao.ma \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=tytso@mit.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 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.