[PATCH 08/10] Keep the __init functions after initialization

From: Catalin Marinas
Date: Mon Jul 10 2006 - 18:10:41 EST


From: Catalin Marinas <catalin.marinas@xxxxxxx>

This patch adds the CONFIG_DEBUG_KEEP_INIT option which preserves the
.init.text section after initialization. Memory leaks happening during this
phase can be more easily tracked.

Signed-off-by: Catalin Marinas <catalin.marinas@xxxxxxx>
---

include/linux/init.h | 4 ++++
lib/Kconfig.debug | 10 ++++++++++
2 files changed, 14 insertions(+), 0 deletions(-)

diff --git a/include/linux/init.h b/include/linux/init.h
index 6667785..1590e9a 100644
--- a/include/linux/init.h
+++ b/include/linux/init.h
@@ -40,7 +40,11 @@ #include <linux/compiler.h>

/* These are for everybody (although not all archs will actually
discard it in modules) */
+#ifdef CONFIG_DEBUG_KEEP_INIT
+#define __init
+#else
#define __init __attribute__ ((__section__ (".init.text")))
+#endif
#define __initdata __attribute__ ((__section__ (".init.data")))
#define __exitdata __attribute__ ((__section__(".exit.data")))
#define __exit_call __attribute_used__ __attribute__ ((__section__ (".exitcall.exit")))
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 6c56be2..5013375 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -171,6 +171,16 @@ config DEBUG_MEMLEAK_ORPHAN_FREEING
information displayed allow an easier identification of
false positives.

+config DEBUG_KEEP_INIT
+ bool "Do not free the __init functions"
+ default n
+ depends on DEBUG_MEMLEAK
+ help
+ This option moves the __init functions out of the .init.text
+ section and therefore they are no longer freed after the
+ kernel initialization. It is useful for identifying memory
+ leaks happening during the kernel or modules initialization.
+
config DEBUG_PREEMPT
bool "Debug preemptible kernel"
depends on DEBUG_KERNEL && PREEMPT && TRACE_IRQFLAGS_SUPPORT
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/