From: Catalin Marinas <catalin.marinas@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.18-rc6 08/10] Keep the __init functions after initialization
Date: Wed, 06 Sep 2006 23:37:35 +0100 [thread overview]
Message-ID: <20060906223734.21550.23139.stgit@localhost.localdomain> (raw)
In-Reply-To: <20060906223536.21550.55411.stgit@localhost.localdomain>
From: Catalin Marinas <catalin.marinas@arm.com>
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@arm.com>
---
include/linux/init.h | 5 +++++
lib/Kconfig.debug | 12 ++++++++++++
2 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/include/linux/init.h b/include/linux/init.h
index 6667785..4b2df24 100644
--- a/include/linux/init.h
+++ b/include/linux/init.h
@@ -40,8 +40,13 @@ #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
+#define __initdata
+#else
#define __init __attribute__ ((__section__ (".init.text")))
#define __initdata __attribute__ ((__section__ (".init.data")))
+#endif
#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 1786cb5..b36ac64 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -195,6 +195,18 @@ config DEBUG_MEMLEAK_REPORTS_NR
reading the /sys/kernel/debug/memleak file could lead to
some soft-locks.
+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
next prev parent reply other threads:[~2006-09-06 22:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 22:35 [PATCH 2.6.18-rc6 00/10] Kernel memory leak detector 0.10 Catalin Marinas
2006-09-06 22:36 ` [PATCH 2.6.18-rc6 01/10] Base support for kmemleak Catalin Marinas
2006-09-06 22:36 ` [PATCH 2.6.18-rc6 02/10] Some documentation " Catalin Marinas
2006-09-06 22:36 ` [PATCH 2.6.18-rc6 03/10] Add the memory allocation/freeing hooks " Catalin Marinas
2006-09-06 22:36 ` [PATCH 2.6.18-rc6 04/10] Modules support " Catalin Marinas
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 05/10] Add kmemleak support for i386 Catalin Marinas
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 06/10] Add kmemleak support for ARM Catalin Marinas
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 07/10] Remove some of the kmemleak false positives Catalin Marinas
2006-09-06 22:37 ` Catalin Marinas [this message]
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 09/10] Simple testing for kmemleak Catalin Marinas
2006-09-06 22:37 ` [PATCH 2.6.18-rc6 10/10] Update the MAINTAINERS file " Catalin Marinas
2006-09-07 0:10 ` [PATCH 2.6.18-rc6 00/10] Kernel memory leak detector 0.10 Michal Piotrowski
2006-09-07 8:04 ` Catalin Marinas
2006-09-07 8:35 ` Michal Piotrowski
2006-09-07 8:37 ` Catalin Marinas
2006-09-07 8:40 ` Michal Piotrowski
2006-09-07 8:52 ` Catalin Marinas
2006-09-07 9:05 ` Michal Piotrowski
2006-09-07 9:10 ` Catalin Marinas
2006-09-07 9:35 ` Michal Piotrowski
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=20060906223734.21550.23139.stgit@localhost.localdomain \
--to=catalin.marinas@gmail.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