mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Tejun Heo <tj@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: early kernel crash when kmemleak is enabled
Date: Fri, 27 May 2011 22:37:54 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1105272236050.3078@ionos> (raw)
In-Reply-To: <20110527202503.GA2769@joi.lan>

On Fri, 27 May 2011, Marcin Slusarz wrote:
> On Thu, May 19, 2011 at 03:08:53PM +0100, Catalin Marinas wrote:
> > 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.
> > 
> 
> With this patch applied kernel didn't panic, but kmemleak did not work either:
> 
> kmemleak: Early log buffer exceeded, please increase DEBUG_KMEMLEAK_EARLY_LOG_SIZE
> kmemleak: Kernel memory leak detector disabled
> 
> I increased DEBUG_KMEMLEAK_EARLY_LOG_SIZE from 400 to 1000, and it crashed in
> exactly the same way:

...
 
> The problem is: debugobjects want to use workqueues (system_wq actually), but they
> are initialized much later in a boot process.
> 
> Attached patch fixes this issue for me.
> 
> 
> diff --git a/lib/debugobjects.c b/lib/debugobjects.c
> index 9d86e45..a78b7c6 100644
> --- a/lib/debugobjects.c
> +++ b/lib/debugobjects.c
> @@ -198,7 +198,7 @@ static void free_object(struct debug_obj *obj)
>  	 * initialized:
>  	 */
>  	if (obj_pool_free > ODEBUG_POOL_SIZE && obj_cache)
> -		sched = !work_pending(&debug_obj_work);
> +		sched = keventd_up() && !work_pending(&debug_obj_work);
>  	hlist_add_head(&obj->node, &obj_pool);
>  	obj_pool_free++;
>  	obj_pool_used--;
> 

Sigh, yes. Care to resend with changelog and signed-off-by ?

Thanks,

	tglx

  reply	other threads:[~2011-05-27 20:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 10:55 Marcin Slusarz
2011-05-19 13:42 ` Tejun Heo
2011-05-19 13:48   ` Catalin Marinas
2011-05-19 13:54     ` Tejun Heo
2011-05-19 14:08       ` Catalin Marinas
2011-05-27 20:25         ` Marcin Slusarz
2011-05-27 20:37           ` Thomas Gleixner [this message]
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=alpine.LFD.2.02.1105272236050.3078@ionos \
    --to=tglx@linutronix.de \
    --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=tj@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

Powered by JetHome