From: Martin Schlemmer <azarah@gentoo.org>
To: KML <linux-kernel@vger.kernel.org>
Cc: akpm@digeo.com
Subject: Slab corruption with ext3-handle-cache.patch
Date: 06 Apr 2003 00:13:10 +0200 [thread overview]
Message-ID: <1049580790.29758.8.camel@nosferatu.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
Hi
I tried this patch a few days again, but not in the mm patch set. So
when I got problems with slab corruption, I figured it was maybe a
patch I missed, and dropped it.
Now with 2.5.66-bk10+, it is merged, and I get it again.
----------------------------------------------------------
Slab corruption: start=cfaeecc4, expend=cfaeee77, problemat=cfaeed28
Last user: [<c01890de>](ext3_destroy_inode+0x1b/0x1f)
Data:
****************************************************************************************************3C 26 99 DF *******************************************************************************************************************************************************************************************************************************************************************************************************************************************A5
Next: 71 F0 2C .DE 90 18 C0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00
slab error in check_poison_obj(): cache `ext3_inode_cache': object was
modified after freeing
Call Trace:
[<c0137894>] check_poison_obj+0x14f/0x18f
[<c0138c8b>] kmem_cache_alloc+0x11c/0x141
[<c01890aa>] ext3_alloc_inode+0x18/0x31
[<c01890aa>] ext3_alloc_inode+0x18/0x31
[<c0162c0c>] alloc_inode+0x1c/0x13d
[<c0163510>] new_inode+0x13/0x7d
[<c017fcf2>] ext3_new_inode+0x41/0x7c7
[<c0138c8b>] kmem_cache_alloc+0x11c/0x141
[<c018de05>] start_this_handle+0x94/0x1b9
[<c018df46>] new_handle+0x1c/0x50
[<c018e025>] journal_start+0xab/0xd2
[<c0187fb4>] ext3_symlink+0xd6/0x2bd
[<c015a4c7>] vfs_symlink+0x5c/0xa3
[<c015a5f0>] sys_symlink+0xe2/0xf2
[<c010a8fd>] sysenter_past_esp+0x52/0x71
-----------------------------------------------------------
If you need more info, just ask.
Regards,
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-04-05 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-05 22:13 Martin Schlemmer [this message]
2003-04-05 22:38 ` Andrew Morton
2003-04-05 22:44 ` Martin Schlemmer
2003-04-05 23:10 ` Andrew Morton
2003-04-05 23:18 ` Martin Schlemmer
2003-04-05 23:22 ` Martin Schlemmer
2003-04-09 22:25 ` Martin Schlemmer
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=1049580790.29758.8.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®