[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tnxiq6sm1c2.fsf@e102109-lin.cambridge.arm.com>
Date: Thu, 13 May 2010 13:29:49 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Tvrtko Ursulin <tvrtko.ursulin@...hos.com>
Cc: Pekka Enberg <penberg@...helsinki.fi>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Airlie <airlied@...ux.ie>
Subject: Re: 2.6.33.2 kmalloc-8 slab leaks ~512 objects per second
Tvrtko Ursulin <tvrtko.ursulin@...hos.com> wrote:
> On Wednesday 12 May 2010 14:00:51 Pekka Enberg wrote:
>> [snip]
>>
>> You might want to try out the built-in kernel memory leak detector.
>> See Documentation/kmemleak.txt for details how to enable it and use
>> it.
>
> Thanks for the suggestion, I will have to try it out once but not this time :)
> because 2.6.34-rc7 seems to be fine, or in other words not leaking.
You could just enable CONFIG_DEBUG_KMEMLEAK on 2.6.33, mount the debugfs
and do a 'cat /sys/kernel/debug/kmemleak' after a half-hour or so.
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists