From: Catalin Marinas <catalin.marinas@arm.com>
To: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Airlie <airlied@linux.ie>
Subject: Re: 2.6.33.2 kmalloc-8 slab leaks ~512 objects per second
Date: Thu, 13 May 2010 13:29:49 +0100 [thread overview]
Message-ID: <tnxiq6sm1c2.fsf@e102109-lin.cambridge.arm.com> (raw)
In-Reply-To: <201005121404.49720.tvrtko.ursulin@sophos.com> (Tvrtko Ursulin's message of "Wed, 12 May 2010 14:04:48 +0100")
Tvrtko Ursulin <tvrtko.ursulin@sophos.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
next prev parent reply other threads:[~2010-05-13 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 10:21 Tvrtko Ursulin
2010-05-12 13:00 ` Pekka Enberg
2010-05-12 13:04 ` Tvrtko Ursulin
2010-05-13 12:29 ` Catalin Marinas [this message]
2010-05-13 12:39 ` Tvrtko Ursulin
2010-05-26 9:21 ` David Rientjes
2010-05-26 16:22 ` Tvrtko Ursulin
[not found] <11758_1273660249_4BEA8359_11758_1675_1_201005121121.49135.tvrtko.ursulin@sophos.com>
2010-05-12 10:38 ` Tvrtko Ursulin
2010-05-12 10:50 ` Tvrtko Ursulin
2010-05-12 13:29 ` Jerome Glisse
2010-05-12 13:37 ` Tvrtko Ursulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tnxiq6sm1c2.fsf@e102109-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=tvrtko.ursulin@sophos.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®