Re: [PATCH 2.6.18-rc4 00/10] Kernel memory leak detector 0.9

[Michal Piotrowski]

On 18/08/06, Catalin Marinas <catalin.marinas@xxxxxxxxx> wrote:
> On 18/08/06, Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> wrote:
> > Lockdep still detects this bug
> >
> > =======================================================
> > [ INFO: possible circular locking dependency detected ]
> > -------------------------------------------------------
> > events/0/8 is trying to acquire lock:
> >  (memleak_lock){++..}, at: [<c0176a11>] memleak_free+0x9e/0x16f
> >
> > but task is already holding lock:
> >  (&parent->list_lock){++..}, at: [<c0174f29>] drain_array+0x49/0xad
> >
> > which lock already depends on the new lock.
> > etc.
>
> Do you have the complete dmesg output? There should be a different
> path which I missed (I didn't get this yestarday but I haven't tried
> with the latest patch I sent to you today).

Here is dmesg output
http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.9/kml-dmesg2

> --
> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/