linux-kernel - Re: [BUG] 2.6.27-rc5 couldn't boot on tulsa machine randomly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1221038340.2442.70.camel@twins.programming.kicks-ass.net>
Date:	Wed, 10 Sep 2008 11:19:00 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] 2.6.27-rc5 couldn't boot on tulsa machine randomly

On Wed, 2008-09-10 at 17:12 +0800, Zhang, Yanmin wrote:
> On Tue, 2008-09-09 at 11:26 +0800, Zhang, Yanmin wrote:
> > On my tulsa x86-64 machine, kernel 2.6.25-rc5 couldn't boot randomly.
> > 
> > Basically, function __enable_runtime forgets to reset  rt_rq->rt_throttled to 0.
> Peter,
> 
> Is there any issue with the patch?

No, just got lost in my inbox due to me getting distracted at the wrong
moment, sorry!

> I tested 2.6.27-rc6 and it still couldn't boot on my tulsa machine. With my patch,
> kernel could boot.

> > When every cpu is up, per-cpu migration_thread is created and it runs very fast,
> > sometimes to mark the corresponding rt_rq->rt_throttled to 1 very quickly. After
> > all cpus are up, with below calling chain,
> > sched_init_smp => arch_init_sched_domains => build_sched_domains => ...
> > => cpu_attach_domain => rq_attach_root => set_rq_online => ... => __enable_runtime,
> > __enable_runtime is called against every rt_rq again, so rt_rq->rt_time is reset to
> > 0, but rt_rq->rt_throttled might be still 1. Later on function do_sched_rt_period_timer
> > couldn't reset it, and all RT tasks couldn't be scheduled to run on that cpu.
> > here is RT task migration_thread which is woken up when a task is migrated to another cpu.
> > 
> > Below patch fixes it against 2.6.27-rc5.
> > 
> > Signed-off-by: Zhang Yanmin <yanmin_zhang@...ux.intel.com>

Acked-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>

Ingo, please push to Linus.

> > ---
> > 
> > diff -Nraup linux-2.6.27-rc5/kernel/sched_rt.c linux-2.6.27-rc5_fix/kernel/sched_rt.c
> > --- linux-2.6.27-rc5/kernel/sched_rt.c	2008-09-09 11:06:43.000000000 +0800
> > +++ linux-2.6.27-rc5_fix/kernel/sched_rt.c	2008-09-09 11:13:04.000000000 +0800
> > @@ -350,6 +350,7 @@ static void __enable_runtime(struct rq *
> >  		spin_lock(&rt_rq->rt_runtime_lock);
> >  		rt_rq->rt_runtime = rt_b->rt_runtime;
> >  		rt_rq->rt_time = 0;
> > +		rt_rq->rt_throttled = 0;
> >  		spin_unlock(&rt_rq->rt_runtime_lock);
> >  		spin_unlock(&rt_b->rt_runtime_lock);
> >  	}
> > 
> > 
> > --
> > 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/
> 

--
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/