From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 13/15] kmemleak: Keep the __init functions after initialization
Date: Wed, 10 Dec 2008 18:28:06 +0000 [thread overview]
Message-ID: <20081210182806.30323.62122.stgit@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20081210182652.30323.4594.stgit@pc1117.cambridge.arm.com>
This patch adds the CONFIG_DEBUG_KEEP_INIT option which preserves the
.init.* sections after initialization. Memory leaks happening during
this phase can be more easily tracked.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
---
include/linux/init.h | 6 ++++++
lib/Kconfig.debug | 12 ++++++++++++
2 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/include/linux/init.h b/include/linux/init.h
index 68cb026..41321ad 100644
--- a/include/linux/init.h
+++ b/include/linux/init.h
@@ -40,9 +40,15 @@
/* These are for everybody (although not all archs will actually
discard it in modules) */
+#ifdef CONFIG_DEBUG_KEEP_INIT
+#define __init
+#define __initdata
+#define __initconst
+#else
#define __init __section(.init.text) __cold notrace
#define __initdata __section(.init.data)
#define __initconst __section(.init.rodata)
+#endif
#define __exitdata __section(.exit.data)
#define __exit_call __used __section(.exitcall.exit)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 1e59827..72cde77 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -313,6 +313,18 @@ config DEBUG_MEMLEAK
In order to access the memleak file, debugfs needs to be
mounted (usually at /sys/kernel/debug).
+config DEBUG_KEEP_INIT
+ bool "Do not free the __init code/data"
+ default n
+ depends on DEBUG_MEMLEAK
+ help
+ This option moves the __init code/data out of the
+ .init.text/.init.data sections. It is useful for identifying
+ memory leaks happening during the kernel or modules
+ initialization.
+
+ If unsure, say N.
+
config DEBUG_PREEMPT
bool "Debug preemptible kernel"
depends on DEBUG_KERNEL && PREEMPT && (TRACE_IRQFLAGS_SUPPORT || PPC64)
next prev parent reply other threads:[~2008-12-10 18:32 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 18:26 [PATCH 00/15] Kernel memory leak detector Catalin Marinas
2008-12-10 18:26 ` [PATCH 01/15] kmemleak: Add the base support Catalin Marinas
2008-12-11 22:01 ` Pekka Enberg
2008-12-12 11:36 ` Catalin Marinas
2008-12-12 13:14 ` Pekka Enberg
2008-12-16 19:36 ` Paul E. McKenney
2008-12-17 9:44 ` Catalin Marinas
2008-12-17 17:15 ` Paul E. McKenney
2008-12-10 18:27 ` [PATCH 02/15] kmemleak: Add documentation on the memory leak detector Catalin Marinas
2008-12-10 18:27 ` [PATCH 03/15] kmemleak: Add the slab memory allocation/freeing hooks Catalin Marinas
2008-12-10 18:32 ` Dave Hansen
2008-12-10 18:53 ` Dave Hansen
2008-12-11 21:22 ` Pekka Enberg
2008-12-12 14:27 ` Catalin Marinas
2008-12-18 10:46 ` Pekka Enberg
2008-12-18 16:38 ` Catalin Marinas
2008-12-18 16:49 ` Christoph Lameter
2008-12-18 17:02 ` Catalin Marinas
2008-12-18 19:35 ` Christoph Lameter
2008-12-18 20:06 ` Pekka Enberg
2008-12-18 21:41 ` Christoph Lameter
2008-12-19 10:44 ` Catalin Marinas
2008-12-10 18:27 ` [PATCH 04/15] kmemleak: Add the slob " Catalin Marinas
2008-12-10 18:36 ` Matt Mackall
2008-12-11 9:47 ` Catalin Marinas
2008-12-11 21:37 ` Pekka Enberg
2008-12-10 18:27 ` [PATCH 05/15] kmemleak: Add the slub " Catalin Marinas
2008-12-11 21:30 ` Pekka Enberg
2008-12-12 13:45 ` Catalin Marinas
2008-12-18 10:51 ` Pekka Enberg
2008-12-18 15:28 ` Catalin Marinas
2008-12-18 16:05 ` Pekka Enberg
2008-12-10 18:27 ` [PATCH 06/15] kmemleak: Add the vmalloc " Catalin Marinas
2008-12-10 18:27 ` [PATCH 07/15] kmemleak: Add memleak_alloc callback from alloc_large_system_hash Catalin Marinas
2008-12-10 19:04 ` Dave Hansen
2008-12-11 9:50 ` Catalin Marinas
2008-12-11 10:08 ` Catalin Marinas
2008-12-11 17:30 ` Dave Hansen
2008-12-11 17:38 ` Catalin Marinas
2008-12-11 17:45 ` Dave Hansen
2008-12-11 19:47 ` Pekka Enberg
2008-12-12 17:04 ` Catalin Marinas
2008-12-12 17:17 ` Dave Hansen
2008-12-12 17:43 ` Catalin Marinas
2008-12-10 18:27 ` [PATCH 08/15] kmemleak: Add modules support Catalin Marinas
2008-12-10 18:27 ` [PATCH 09/15] x86: Provide _sdata in the vmlinux_*.lds.S files Catalin Marinas
2008-12-10 18:27 ` [PATCH 10/15] arm: Provide _sdata and __bss_stop in the vmlinux.lds.S file Catalin Marinas
2008-12-10 18:27 ` [PATCH 11/15] kmemleak: Remove some of the kmemleak false positives Catalin Marinas
2008-12-10 18:28 ` [PATCH 12/15] kmemleak: Enable the building of the memory leak detector Catalin Marinas
2008-12-10 19:20 ` Dave Hansen
2008-12-12 17:27 ` Catalin Marinas
2008-12-12 18:02 ` Dave Hansen
2008-12-10 18:28 ` Catalin Marinas [this message]
2008-12-10 18:44 ` [PATCH 13/15] kmemleak: Keep the __init functions after initialization Sam Ravnborg
2008-12-17 13:09 ` Catalin Marinas
2008-12-10 18:28 ` [PATCH 14/15] kmemleak: Simple testing module for kmemleak Catalin Marinas
2008-12-10 18:28 ` [PATCH 15/15] kmemleak: Add the corresponding MAINTAINERS entry Catalin Marinas
2008-12-11 9:44 ` [PATCH 00/15] Kernel memory leak detector Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2008-11-29 10:43 Catalin Marinas
2008-11-29 10:44 ` [PATCH 13/15] kmemleak: Keep the __init functions after initialization 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=20081210182806.30323.62122.stgit@pc1117.cambridge.arm.com \
--to=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
all inboxes | Powered by JetHome®