From: Tejun Heo <tj@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Marcin Slusarz <marcin.slusarz@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Dipankar Sarma <dipankar@in.ibm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: early kernel crash when kmemleak is enabled
Date: Thu, 19 May 2011 15:54:25 +0200 [thread overview]
Message-ID: <20110519135425.GI627@htj.dyndns.org> (raw)
In-Reply-To: <1305812924.26710.41.camel@e102109-lin.cambridge.arm.com>
On Thu, May 19, 2011 at 02:48:44PM +0100, Catalin Marinas wrote:
> Thanks for tracking this down. Untested (I can add a log afterwards):
>
> diff --git a/init/main.c b/init/main.c
> index 4a9479e..48df882 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -580,8 +580,8 @@ asmlinkage void __init start_kernel(void)
> #endif
> page_cgroup_init();
> enable_debug_pagealloc();
> - kmemleak_init();
> debug_objects_mem_init();
> + kmemleak_init();
> setup_per_cpu_pageset();
> numa_policy_init();
> if (late_time_init)
Heh, that was swift. Yeap, seems to work here. Please feel free to
add my Tested-by.
Thank you.
--
tejun
next prev parent reply other threads:[~2011-05-19 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-15 10:55 early kernel crash when kmemleak is enabled Marcin Slusarz
2011-05-19 13:42 ` Tejun Heo
2011-05-19 13:48 ` Catalin Marinas
2011-05-19 13:54 ` Tejun Heo [this message]
2011-05-19 14:08 ` Catalin Marinas
2011-05-27 20:25 ` Marcin Slusarz
2011-05-27 20:37 ` Thomas Gleixner
2011-05-28 11:23 ` [PATCH] debugobjects: fix boot crash when both kmemleak and debugobjects are enabled (was: Re: early kernel crash when kmemleak is enabled) Marcin Slusarz
2011-06-19 20:43 ` Marcin Slusarz
2011-06-20 12:43 ` [tip:core/urgent] debugobjects: Fix boot crash when kmemleak and debugobjects enabled tip-bot for Marcin Slusarz
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=20110519135425.GI627@htj.dyndns.org \
--to=tj@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).