From: Daniel Baluta <dbaluta@ixiacom.com>
To: paulmck@linux.vnet.ibm.com
Cc: akpm@linux-foundation.org, mingo@elte.hu, fweisbec@gmail.com,
rdunlap@xenotime.net, linux-kernel@vger.kernel.org,
catalin.marinas@arm.com, Daniel Baluta <dbaluta@ixiacom.com>
Subject: [PATCH] kmemleak: build kmemleak-test.c as a module-only
Date: Wed, 16 Mar 2011 20:16:34 +0200 [thread overview]
Message-ID: <1300299394-20844-1-git-send-email-dbaluta@ixiacom.com> (raw)
mm/kmemleak-test.c is used to provide an example of how kmemleak
tool works.
Memory is leaked at module unload-time, so building the test
in kernel (Y) makes the leaks impossible and the test useless.
Qualify DEBUG_KMEMLEAK_TEST config symbol with "depends on m",
to restrict module-only building.
Signed-off-by: Daniel Baluta <dbaluta@ixiacom.com>
---
lib/Kconfig.debug | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 689f311..6e9cacc 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -407,11 +407,9 @@ config DEBUG_KMEMLEAK_EARLY_LOG_SIZE
config DEBUG_KMEMLEAK_TEST
tristate "Simple test for the kernel memory leak detector"
- depends on DEBUG_KMEMLEAK
+ depends on DEBUG_KMEMLEAK && m
help
- Say Y or M here to build a test for the kernel memory leak
- detector. This option enables a module that explicitly leaks
- memory.
+ This option enables a module that explicitly leaks memory.
If unsure, say N.
--
1.7.1
next reply other threads:[~2011-03-16 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 18:16 Daniel Baluta [this message]
2011-03-23 11:18 ` Daniel Baluta
2011-03-23 11:23 ` Pekka Enberg
2011-03-23 11:24 ` Catalin Marinas
2011-03-25 14:05 ` Daniel Baluta
2011-03-30 15:02 ` Daniel Baluta
2011-03-30 15:24 ` Randy Dunlap
2011-03-31 7:44 ` Daniel Baluta
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=1300299394-20844-1-git-send-email-dbaluta@ixiacom.com \
--to=dbaluta@ixiacom.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rdunlap@xenotime.net \
/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®