lkml.org 
[lkml]   [2006]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 2.6.18-rc4 00/10] Kernel memory leak detector 0.9
On 18/08/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> I just added your "Fix memory leak in vc_resize/vc_allocate" patch to
> my series file.
>
> orphan pointer 0xc6110000 (size 12288):
> c017480e: <__kmalloc>
> c024dda4: <vc_resize>
> c020ed9c: <fbcon_startup>
> c0251028: <register_con_driver>
> c02511e0: <take_over_console>
> c020e21e: <fbcon_takeover>
> c0212b08: <fbcon_fb_registered>
> c0212ce1: <fbcon_event_notify>
> orphan pointer 0xf55b0000 (size 8208):
> c017480e: <__kmalloc>
> c0211bb8: <fbcon_set_font>
> c0251b17: <con_font_set>
> c0251c7b: <con_font_op>
> c0249a97: <vt_ioctl>
> c024432e: <tty_ioctl>
> c0189fd1: <do_ioctl>
> c018a269: <vfs_ioctl>

The second one is probably a false positive as the stored pointer is
different from the one returned by kmalloc (there is some padding).
I'll add it to the kmemleak-false-positives patch.

The first one might be a real leak. Anotonino, any idea about this?

Thanks.

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

\
 
 \ /
  Last update: 2006-08-19 12:09    [W:0.088 / U:4.004 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site