From: Yinghai Lu <yinghai@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
"H. Peter Anvin" <hpa@zytor.com>, stable <stable@kernel.org>
Subject: Re: [PATCH] kmemleak: Add support for NO_BOOTMEM configurations
Date: Thu, 15 Jul 2010 10:16:54 -0700 [thread overview]
Message-ID: <4C3F4286.3070503@kernel.org> (raw)
In-Reply-To: <20100715145834.20885.20341.stgit@e102109-lin.cambridge.arm.com>
should be for 2.6.34 and 2.6.35.
Thanks
Yinghai
On 07/15/2010 07:58 AM, Catalin Marinas wrote:
> With commits 08677214 and 59be5a8e, alloc_bootmem()/free_bootmem() and
> friends use the early_res functions for memory management when
> NO_BOOTMEM is enabled. This patch adds the kmemleak calls in the
> corresponding code paths for bootmem allocations.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Pekka Enberg <penberg@cs.helsinki.fi>
> Cc: Yinghai Lu <yinghai@kernel.org>
> Cc: H. Peter Anvin <hpa@zytor.com>
> ---
> kernel/early_res.c | 6 ++++++
> mm/page_alloc.c | 5 +++++
> 2 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/early_res.c b/kernel/early_res.c
> index 31aa933..7bfae88 100644
> --- a/kernel/early_res.c
> +++ b/kernel/early_res.c
> @@ -7,6 +7,8 @@
> #include <linux/bootmem.h>
> #include <linux/mm.h>
> #include <linux/early_res.h>
> +#include <linux/slab.h>
> +#include <linux/kmemleak.h>
>
> /*
> * Early reserved memory areas.
> @@ -319,6 +321,8 @@ void __init free_early(u64 start, u64 end)
> struct early_res *r;
> int i;
>
> + kmemleak_free_part(__va(start), end - start);
> +
> i = find_overlapped_early(start, end);
> r = &early_res[i];
> if (i >= max_early_res || r->end != end || r->start != start)
> @@ -333,6 +337,8 @@ void __init free_early_partial(u64 start, u64 end)
> struct early_res *r;
> int i;
>
> + kmemleak_free_part(__va(start), end - start);
> +
> if (start == end)
> return;
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 431214b..68319dd 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -3659,6 +3659,11 @@ void * __init __alloc_memory_core_early(int nid, u64 size, u64 align,
> ptr = phys_to_virt(addr);
> memset(ptr, 0, size);
> reserve_early_without_check(addr, addr + size, "BOOTMEM");
> + /*
> + * The min_count is set to 0 so that bootmem allocated blocks
> + * are never reported as leaks.
> + */
> + kmemleak_alloc(ptr, size, 0, 0);
> return ptr;
> }
>
next prev parent reply other threads:[~2010-07-15 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 14:58 [PATCH] kmemleak: Add support for NO_BOOTMEM configurations Catalin Marinas
2010-07-15 17:16 ` Yinghai Lu [this message]
2010-07-16 8:46 ` Catalin Marinas
2010-07-16 18:43 ` Yinghai Lu
2010-07-16 9:01 ` 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=4C3F4286.3070503@kernel.org \
--to=yinghai@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=stable@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