lkml.org 
[lkml]   [2006]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 00/10] Kernel memory leak detector 0.8
On 11/07/06, Catalin Marinas <catalin.marinas@gmail.com> wrote:
> On 11/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> > So if we got 3970
> > orphan pointer 0xf5a6fd60 (size 39):
> > c0173822: <__kmalloc>
> > c01df500: <context_struct_to_string>
> [...]
> > and 4673
> > orphan pointer 0xf4249488 (size 29):
> > c0173822: <__kmalloc>
> > c01df500: <context_struct_to_string>
> [...]
> > It's not a memleak?
>
> Not exactly. What I meant is that if you have a corresponding number
> of reports from __alloc_skb, maybe they were false positives and the
> block wasn't scanned leading to other false positive reports
>
> It looks like there are some reports in __alloc_skb. Please try the
> attached patch.

Here is the result
http://www.stardust.webpages.pl/files/o_bugs/kml/ml4.txt

>
> Thanks.
>
> --
> Catalin
>
>
>

Regards,
Michal

--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
-
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-07-11 19:03    [W:0.104 / U:0.724 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site