Re: -rc3 leaking NOT BIO [Was: Memory leak in 2.6.11-rc1?]

[Andrew Morton]

Parag Warudkar <kernel-stuff@xxxxxxxxxxx> wrote:
>
> On Wednesday 16 February 2005 12:12 am, Andrew Morton wrote:
> > echo "size-4096 0 0 0" > /proc/slabinfo
> 
> Is there a reason X86_64 doesnt have CONFIG_FRAME_POINTER anywhere in 
> the .config?

No good reason, I suspect.

> I tried -rc4 with Manfred's patch and with CONFIG_DEBUG_SLAB and 
> CONFIG_DEBUG.

Thanks.

> I get the following output from
> echo "size-64 0 0 0" > /proc/slabinfo
> 
> obj ffff81002fe80000/0: 00000000000008a8 <0x8a8>
> obj ffff81002fe80000/1: 00000000000008a8 <0x8a8>
> obj ffff81002fe80000/2: 00000000000008a8 <0x8a8>
> :                                 3
> :                                 4
> :                                 :
> obj ffff81002fe80000/43: 00000000000008a8 <0x8a8>
> obj ffff81002fe80000/44: 00000000000008a8 <0x8a8>
>  
> How do I know what is at ffff81002fe80000? I tried the normal tricks (gdb 
> -c /proc/kcore vmlinux, objdump -d etc.) but none of the places list this 
> address.

ffff81002fe80000 is the address of the slab object.  00000000000008a8 is
supposed to be the caller's text address.  It appears that
__builtin_return_address(0) is returning junk.  Perhaps due to
-fomit-frame-pointer.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/