From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, Manfred Spraul <manfred@colorfullife.com>
Subject: Re: Oops: 2.5.64 check_obj_poison for 'size-64'
Date: Fri, 7 Mar 2003 04:53:01 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.50.0303070450290.18716-100000@montezuma.mastecende.com> (raw)
In-Reply-To: <20030307010539.3c0a14a3.akpm@digeo.com>
On Fri, 7 Mar 2003, Andrew Morton wrote:
> > [root@dev16-002 root]# Slab corruption: start=db0bbc44, expend=db0bbc83, problemat=db0bbc48
> > Data: ....71 F0 2C .........................................................
> > Next: 71 F0 2C .71 F0 2C .........................
> > slab error in check_poison_obj(): cache `size-64': object was modified after freeing
> > Call Trace:
> > [<c0142319>] check_poison_obj+0x119/0x130
> > [<c0143c92>] kmalloc+0xd2/0x180
> > [<c0166188>] pipe_new+0x28/0xd0
> > [<c0166263>] get_pipe_inode+0x23/0xb0
> > [<c0166322>] do_pipe+0x32/0x1e0
> > [<c01704ac>] dput+0x1c/0x2b0
> > [<c016661e>] getname+0x5e/0xa0
> > [<c012f9b0>] sigprocmask+0xe0/0x150
> > [<c012fb9a>] sys_rt_sigprocmask+0x17a/0x190
> > [<c0111ed3>] sys_pipe+0x13/0x60
> > [<c010ad9b>] syscall_call+0x7/0xb
>
> I don't see any clues there.
>
> This is a bad, bad bug. How are you triggering it?
Very hard to trigger, currently it's happening whilst the system appears
to be idle so i'm trying to track down what processes there are when the
trigger happens.
> Manfred, would it be possible to add builtin_return_address(0) into each
> object, so we can find out who did the initial kmalloc (or kfree, even)?
>
> It'll probably require CONFIG_FRAME_POINTER.
Zwane
--
function.linuxpower.ca
next prev parent reply other threads:[~2003-03-07 9:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 5:13 Oops: 2.5.64 check_obj_poison for 'size-64' Zwane Mwaikambo
2003-03-07 6:23 ` Andrew Morton
2003-03-07 7:22 ` Zwane Mwaikambo
2003-03-07 7:35 ` Andrew Morton
2003-03-07 7:40 ` Zwane Mwaikambo
2003-03-07 7:45 ` Miles Bader
2003-03-07 7:58 ` Andrew Morton
2003-03-07 8:10 ` Miles Bader
2003-03-07 10:05 ` [PATCH] protect 'action' in show_interrupts Zwane Mwaikambo
2003-03-07 10:28 ` Andrew Morton
2003-03-07 15:32 ` Zwane Mwaikambo
2003-03-07 15:46 ` Russell King
2003-03-07 16:25 ` Zwane Mwaikambo
2003-03-07 22:01 ` Andrew Morton
[not found] ` <Pine.LNX.4.50.0303070351060.18716-100000@montezuma.mastecende.com>
[not found] ` <20030307010539.3c0a14a3.akpm@digeo.com>
2003-03-07 9:53 ` Zwane Mwaikambo [this message]
2003-03-07 19:38 ` Oops: 2.5.64 check_obj_poison for 'size-64' Manfred Spraul
2003-03-07 21:57 ` Zwane Mwaikambo
2003-03-08 2:11 ` Zwane Mwaikambo
2003-03-08 2:24 ` Andrew Morton
2003-03-08 2:42 ` Zwane Mwaikambo
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=Pine.LNX.4.50.0303070450290.18716-100000@montezuma.mastecende.com \
--to=zwane@linuxpower.ca \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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).