Re: [PATCH 4/4] kmemleak: Report previously found leaks even after an error
From: Catalin Marinas
Date: Tue Oct 04 2011 - 16:50:48 EST
On 4 October 2011 18:45, Nick Bowler <nbowler@xxxxxxxxxxxxxxxx> wrote:
> On 2011-09-29 12:02 +0100, Catalin Marinas wrote:
>> If an error fatal to kmemleak (like memory allocation failure) happens,
>> kmemleak disables itself but it also removes the access to any
>> previously found memory leaks. This patch allows read-only access to the
>> kmemleak debugfs interface but disables any other action.
>> Repored-by: Nick Bowler <nbowler@xxxxxxxxxxxxxxxx>
> Reported-by: ...
I was wondering why you were not automatically cc'ed.
>> Signed-off-by: Catalin Marinas <catalin.marinas@xxxxxxx>
> Cool, I'll try this out. Kmemleak rarely stays alive for more than a
> few days on my desktop before shutting itself down due to an allocation
> failure, so this should be really handy.
You can have a look at /proc/slabinfo and meminfo and see if there are
any really big leaks. In general the kmemleak objects number is higher
than the sum of all the other slab objects (but I haven't done any
statistics). Hopefully kmemleak doesn't leak memory :) (I should add
some simple checks though).
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/