From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: [RFC PATCH 0/3] kmemleak: Add support for the bootmem allocator
Date: Mon, 06 Jul 2009 11:51:43 +0100 [thread overview]
Message-ID: <20090706104654.16051.44029.stgit@pc1117.cambridge.arm.com> (raw)
Hi,
In the last few days, I went through of false positives reported by
kmemleak and it turns out some of them were caused by not tracking
alloc_bootmem* calls. Rather than adding more and more kmemleak
annotations throughout the kernel, I decided to add support for tracking
all the alloc_bootmem* and free_bootmem calls.
The latter may not have a corresponding alloc_bootmem* pair or it may
only free part of a block. I changed kmemleak to support this usage.
Thanks for your feedback.
Catalin Marinas (3):
kmemleak: Remove alloc_bootmem annotations introduced in the past
kmemleak: Add callbacks to the bootmem allocator
kmemleak: Allow partial freeing of memory blocks
include/linux/kmemleak.h | 4 +++
kernel/pid.c | 7 ------
mm/bootmem.c | 36 ++++++++++++++++++++++++------
mm/kmemleak.c | 55 ++++++++++++++++++++++++++++++++++++++++++----
mm/page_alloc.c | 14 +++---------
5 files changed, 86 insertions(+), 30 deletions(-)
--
Catalin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2009-07-06 10:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 10:51 Catalin Marinas [this message]
2009-07-06 10:51 ` [RFC PATCH 1/3] kmemleak: Allow partial freeing of memory blocks Catalin Marinas
2009-07-07 7:12 ` Pekka Enberg
2009-07-07 8:42 ` Catalin Marinas
2009-07-07 13:39 ` Catalin Marinas
2009-07-08 6:40 ` Pekka Enberg
2009-07-08 9:42 ` Catalin Marinas
2009-07-08 9:45 ` Pekka Enberg
2009-07-06 10:51 ` [RFC PATCH 2/3] kmemleak: Add callbacks to the bootmem allocator Catalin Marinas
2009-07-06 10:58 ` Catalin Marinas
2009-07-07 7:08 ` Pekka Enberg
2009-07-07 16:53 ` Johannes Weiner
2009-07-07 22:09 ` Catalin Marinas
2009-07-08 6:48 ` Pekka Enberg
2009-07-08 9:43 ` Catalin Marinas
2009-07-08 11:46 ` Johannes Weiner
2009-07-08 9:46 ` Johannes Weiner
2009-07-08 10:02 ` Catalin Marinas
2009-07-08 10:03 ` Pekka Enberg
2009-07-06 10:52 ` [RFC PATCH 3/3] kmemleak: Remove alloc_bootmem annotations introduced in the past Catalin Marinas
2009-07-07 7:12 ` Pekka Enberg
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=20090706104654.16051.44029.stgit@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/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