On 11/07/06, Catalin Marinas <[email protected]> wrote:
On 11/07/06, Michal Piotrowski <[email protected]> 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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
