[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1305814133.26710.69.camel@e102109-lin.cambridge.arm.com>
Date: Thu, 19 May 2011 15:08:53 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Tejun Heo <tj@...nel.org>
Cc: Marcin Slusarz <marcin.slusarz@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Dipankar Sarma <dipankar@...ibm.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: early kernel crash when kmemleak is enabled
On Thu, 2011-05-19 at 14:54 +0100, Tejun Heo wrote:
> 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.
Thanks. I have two other minor kmemleak fixes, so I'll send Linus a pull
request in the next day or so.
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists