Messages in this thread | | | Date | Fri, 14 Jul 2006 15:53:33 +0100 | From | "Catalin Marinas" <> | Subject | Re: [PATCH 00/10] Kernel memory leak detector 0.8 |
| |
On 13/07/06, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote: > After applying context_struct_to_string-not-leak.patch and reverting > alloc_skb-false-positive.patch I haven't noticed that soft lockup.
You still need the apply alloc_skb-false-positive.patch as it just avoids a false positive (I'll add it to kmemleak 0.9). Does anything change with this (and the context_struct_... one)?
> Here is something new > orphan pointer 0xf40d61ac (size 1536): > c017392a: <__kmalloc_track_caller> > c01631b1: <__kzalloc> > f98869cd: <skge_ring_alloc> > f9888a1d: <skge_up> > c02b17b6: <dev_open> > c02b2e94: <dev_change_flags> > c02e6e17: <devinet_ioctl> > c02e8a02: <inet_ioctl>
This looks like a leak but I couldn't find anything obvious with the code. I'll keep looking.
> http://www.stardust.webpages.pl/files/o_bugs/kml/ml2/ > http://www.stardust.webpages.pl/files/o_bugs/kml/ml3/
I would also need to investigate why the report shows some orphan pointers without any back-trace information. It seems to disappear after a while.
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/
| |