Re: Oops: 2.5.64 check_obj_poison for 'size-64'

Zwane Mwaikambo (
Fri, 7 Mar 2003 16:57:38 -0500 (EST)

On Fri, 7 Mar 2003, Manfred Spraul wrote:

> Andrew Morton wrote:
> >This is a bad, bad bug. How are you triggering it?
> >
> >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.
> >
> >
> No, CONFIG_FRAME_POINTER is only needed for __builtin_return_address(x,
> x>0). _address(0) always works.
> I've attached a patch that records the last kfree address and prints
> that if a poison check fails.
> Zwane, could you try to reproduce the bug?

I can almost always witness it given approx 30minutes of runtime, however
i still don't know how to trigger it by on demand. I'll apply your patch
and get back to you when it triggers next.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at