From: Catalin Marinas <catalin.marinas@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.19 05/10] Add kmemleak support for i386
Date: Thu, 30 Nov 2006 23:00:43 +0000 [thread overview]
Message-ID: <20061130230043.5469.34508.stgit@localhost.localdomain> (raw)
In-Reply-To: <20061130225219.5469.2453.stgit@localhost.localdomain>
This patch modifies the vmlinux.lds.S script and adds the backtrace support
for i386 to be used with kmemleak.
Signed-off-by: Catalin Marinas <catalin.marinas@gmail.com>
---
arch/i386/kernel/vmlinux.lds.S | 4 ++++
include/asm-i386/thread_info.h | 10 +++++++++-
2 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/arch/i386/kernel/vmlinux.lds.S b/arch/i386/kernel/vmlinux.lds.S
index c6f84a0..499c32b 100644
--- a/arch/i386/kernel/vmlinux.lds.S
+++ b/arch/i386/kernel/vmlinux.lds.S
@@ -52,6 +52,7 @@ SECTIONS
/* writeable */
. = ALIGN(4096);
+ _sdata = .; /* Start of data section */
.data : AT(ADDR(.data) - LOAD_OFFSET) { /* Data */
*(.data)
CONSTRUCTORS
@@ -157,6 +158,9 @@ SECTIONS
__per_cpu_start = .;
.data.percpu : AT(ADDR(.data.percpu) - LOAD_OFFSET) { *(.data.percpu) }
__per_cpu_end = .;
+ __memleak_offsets_start = .;
+ .init.memleak_offsets : AT(ADDR(.init.memleak_offsets) - LOAD_OFFSET) { *(.init.memleak_offsets) }
+ __memleak_offsets_end = .;
. = ALIGN(4096);
__init_end = .;
/* freed after init ends here */
diff --git a/include/asm-i386/thread_info.h b/include/asm-i386/thread_info.h
index 54d6d7a..054553f 100644
--- a/include/asm-i386/thread_info.h
+++ b/include/asm-i386/thread_info.h
@@ -100,12 +100,20 @@ static inline struct thread_info *curren
struct thread_info *ret; \
\
ret = kmalloc(THREAD_SIZE, GFP_KERNEL); \
+ memleak_ignore(ret); \
if (ret) \
memset(ret, 0, THREAD_SIZE); \
ret; \
})
#else
-#define alloc_thread_info(tsk) kmalloc(THREAD_SIZE, GFP_KERNEL)
+#define alloc_thread_info(tsk) \
+ ({ \
+ struct thread_info *ret; \
+ \
+ ret = kmalloc(THREAD_SIZE, GFP_KERNEL); \
+ memleak_ignore(ret); \
+ ret; \
+ })
#endif
#define free_thread_info(info) kfree(info)
next prev parent reply other threads:[~2006-11-30 23:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 22:59 [PATCH 2.6.19 00/10] Kernel memory leak detector 0.12 Catalin Marinas
2006-11-30 22:59 ` [PATCH 2.6.19 01/10] Base support for kmemleak Catalin Marinas
2006-11-30 23:00 ` [PATCH 2.6.19 02/10] Kmemleak documentation Catalin Marinas
2006-11-30 23:00 ` [PATCH 2.6.19 03/10] Add the memory allocation/freeing hooks for kmemleak Catalin Marinas
2006-11-30 23:00 ` [PATCH 2.6.19 04/10] Modules support " Catalin Marinas
2006-11-30 23:00 ` Catalin Marinas [this message]
2006-11-30 23:01 ` [PATCH 2.6.19 06/10] Add kmemleak support for ARM Catalin Marinas
2006-11-30 23:01 ` [PATCH 2.6.19 07/10] Remove some of the kmemleak false positives Catalin Marinas
2006-11-30 23:01 ` [PATCH 2.6.19 08/10] Keep the __init functions after initialization Catalin Marinas
2006-11-30 23:01 ` [PATCH 2.6.19 09/10] Simple testing for kmemleak Catalin Marinas
2006-11-30 23:01 ` [PATCH 2.6.19 10/10] Update the MAINTAINERS file " 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=20061130230043.5469.34508.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