From: Catalin Marinas <catalin.marinas@arm.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
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 11:02:35 +0100 [thread overview]
Message-ID: <1247047355.6595.16.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20090708094643.GA1956@cmpxchg.org>
On Wed, 2009-07-08 at 11:46 +0200, Johannes Weiner wrote:
> On Tue, Jul 07, 2009 at 11:09:46PM +0100, Catalin Marinas wrote:
>
> > 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?
> >
> > diff --git a/mm/bootmem.c b/mm/bootmem.c
> > index 5a649a0..74cbb34 100644
> > --- a/mm/bootmem.c
> > +++ b/mm/bootmem.c
> > @@ -520,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;
> > }
>
> Yes, that should work.
Thanks. May I add your Acked-by line to the final patch?
--
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:55 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
2009-07-08 11:46 ` Johannes Weiner
2009-07-08 9:46 ` Johannes Weiner
2009-07-08 10:02 ` Catalin Marinas [this message]
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=1247047355.6595.16.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