Re: [2.6.35-rc6 patch] increase kmemleak robustness at boot

From: Daniel J Blueman
Date: Thu Jul 29 2010 - 08:49:16 EST

On 29 July 2010 12:34, Catalin Marinas <catalin.marinas@xxxxxxxxx> wrote:
> On 28 July 2010 17:49, Pekka Enberg <penberg@xxxxxxxxxxxxxx> wrote:
>> Daniel J Blueman wrote:
>>> I've consistently been experiencing kmemleak exhaust it's 400-entry
>>> early-boot buffer and disabling itself; there have been reports of
>>> this also, and I'm finding this on x86-64 with various debug options
>>> enabled.
>>> If we issue a warning and allow the buffer to wrap, we don't need to
>>> hit the kill-switch. While we lose track of some early potential
>>> leaks, it's better than no functionality.
>>> Let me know if it's acceptable, and many thanks for such an excellent
>>> tool,
>> Is it just potential leaks that we lose or can this cause false positives?
> I wouldn't go this route, it's a great source of false positives.
> Given that it's not always easy to investigate a memory leak, adding
> more false positives would just make people turn the tool off. There
> are several things in place like crc checking and maybe that's why
> Daniel doesn't get false positives but that's not always the case.
> I would rather change the static early alloc buffer with something
> like bootmem allocation (the recursiveness should be bound, kmemleak
> tracks bootmem allocations as well). But I'm on holiday until middle
> of August and not able to do any tests in this area.

Indeed, moving to dynamic early allocation is all the more better. For
now, I'll increase the early allocation to 15200 elements, as the
400-entry buffer wraps 38.

Thanks again,
Daniel J Blueman
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