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

From: Catalin Marinas
Date: Fri Aug 18 2006 - 12:55:08 EST

On 18/08/06, Michal Piotrowski <michal.k.k.piotrowski@xxxxxxxxx> wrote:
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
> 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

Thanks. It is strange - I was under the impression that calling
radix_tree_preload() outside the memleak_lock holding would actually
prevent radix_tree_insert() from allocating a node (and therefore call
kmem_cache_alloc and acquire the list_lock). I'll look at the
radix_tree code this weekend. I'm looking at implementing some kind of
RCU mechanism in kmemleak to avoid future problems (might need changed
to radix_tree as well).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at