From: Catalin Marinas <catalin.marinas@arm.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC PATCH 2/3] kmemleak: Add callbacks to the bootmem allocator
Date: Wed, 08 Jul 2009 10:43:51 +0100 [thread overview]
Message-ID: <1247046231.6595.14.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <1247035701.15919.35.camel@penberg-laptop>
On Wed, 2009-07-08 at 09:48 +0300, Pekka Enberg wrote:
> On Tue, 2009-07-07 at 23:09 +0100, Catalin Marinas wrote:
> > On Tue, 2009-07-07 at 18:53 +0200, Johannes Weiner wrote:
> > > On Tue, Jul 07, 2009 at 10:08:50AM +0300, Pekka Enberg wrote:
> > > > On Mon, 2009-07-06 at 11:51 +0100, Catalin Marinas wrote:
> > > > > @@ -597,7 +601,9 @@ restart:
> > > > > void * __init __alloc_bootmem_nopanic(unsigned long size, unsigned long align,
> > > > > unsigned long goal)
> > > > > {
> > > > > - return ___alloc_bootmem_nopanic(size, align, goal, 0);
> > > > > + void *ptr = ___alloc_bootmem_nopanic(size, align, goal, 0);
> > > > > + kmemleak_alloc(ptr, size, 1, GFP_KERNEL);
> > > > > + return ptr;
> > >
> > > You may get an object from kzalloc() here, I don't think you want to
> > > track that (again), right?
> >
> > You are write, I missed the alloc_arch_preferred_bootmem() function
> > which may call kzalloc().
> >
> > > Pekka already worked out all the central places to catch 'slab already
> > > available' allocations, they can probably help you place the hooks.
> >
> > It seems that alloc_bootmem_core() is central to all the bootmem
> > allocations. Is it OK to place the kmemleak_alloc hook only in this
> > function?
>
> I think so. Johannes?
To get a better view, here's the complete patch:
kmemleak: Add callbacks to the bootmem allocator
From: Catalin Marinas <catalin.marinas@arm.com>
This patch adds kmemleak_alloc/free callbacks to the bootmem allocator.
This would allow scanning of such blocks and help avoiding a whole class
of false positives and more kmemleak annotations.
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>
---
mm/bootmem.c | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/mm/bootmem.c b/mm/bootmem.c
index d2a9ce9..90f3ed0 100644
--- a/mm/bootmem.c
+++ b/mm/bootmem.c
@@ -335,6 +335,8 @@ void __init free_bootmem_node(pg_data_t *pgdat, unsigned long physaddr,
{
unsigned long start, end;
+ kmemleak_free_part(__va(physaddr), size);
+
start = PFN_UP(physaddr);
end = PFN_DOWN(physaddr + size);
@@ -354,6 +356,8 @@ void __init free_bootmem(unsigned long addr, unsigned long size)
{
unsigned long start, end;
+ kmemleak_free_part(__va(addr), size);
+
start = PFN_UP(addr);
end = PFN_DOWN(addr + size);
@@ -516,6 +520,7 @@ find_block:
region = phys_to_virt(PFN_PHYS(bdata->node_min_pfn) +
start_off);
memset(region, 0, size);
+ kmemleak_alloc(region, size, 1, 0);
return region;
}
--
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 prev parent reply other threads:[~2009-07-08 9:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 10:51 [RFC PATCH 0/3] kmemleak: Add support for " Catalin Marinas
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 [this message]
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=1247046231.6595.14.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=hannes@cmpxchg.org \
--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