Re: [PATCH 4/4] kmemleak: Report previously found leaks even afteran error

[Nick Bowler]

On 2011-10-04 21:50 +0100, Catalin Marinas wrote:
> On 4 October 2011 18:45, Nick Bowler <nbowler@xxxxxxxxxxxxxxxx> wrote:
> > 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).

I don't think the failures that cause kmemleak to shut down in my case
are actually caused by a memory leak.  The machine is rather old and
has only 1G of RAM.  I think kmemleak is just failing to allocate during
a period of real memory pressure.

-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
--
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/