From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org
Subject: kmemleak and SLAB
Date: Tue, 4 Oct 2011 07:31:47 +0100 [thread overview]
Message-ID: <20111004063147.GA12229@sucs.org> (raw)
Hi,
When I try to use kmemleak with the SLAB allocator set I receive this
message when booting 3.1-rc8:
[ 28.480569] kmemleak: Cannot allocate a kmemleak_object structure
[ 28.480593] kmemleak: Kernel memory leak detector disabled
[ 34.428037] CPA self-test:
[ 34.435881] 4k 259968 large 0 gb 0 x 259968[b0000000-ef77f000] miss 0
[ 34.447669] 4k 259968 large 0 gb 0 x 259968[b0000000-ef77f000] miss 0
[ 34.458402] 4k 259968 large 0 gb 0 x 259968[b0000000-ef77f000] miss 0
[ 34.458407] ok.
[ 38.754032] wlan0: no IPv6 routers present
[ 67.666048] kmemleak: Automatic memory scanning thread ended
All is fine when using SLUB. On another run I also got an error about an
ODEBUG oom so I wonder if this is indicative of another problem...
--
Sitsofe | http://sucs.org/~sits/
next reply other threads:[~2011-10-04 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 6:31 Sitsofe Wheeler [this message]
2011-10-04 15:41 ` kmemleak and SLAB Catalin Marinas
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=20111004063147.GA12229@sucs.org \
--to=sitsofe@yahoo.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
/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