linux-kernel - Re: BUG: tick device NULL pointer during system initialization and shutdown

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: <alpine.DEB.2.02.1307011518350.4013@ionos.tec.linutronix.de>
Date:	Mon, 1 Jul 2013 15:30:47 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Prarit Bhargava <prarit@...hat.com>
cc:	Linux Kernel <linux-kernel@...r.kernel.org>, athorlton@....com,
	CAI Qian <caiqian@...hat.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: BUG: tick device NULL pointer during system initialization and
 shutdown

On Mon, 1 Jul 2013, Prarit Bhargava wrote:
> On 06/28/2013 06:52 AM, Thomas Gleixner wrote:
> > Huch. Did the warning in the broadcast code trigger before that?
> 
> tglx,
> 
> AFAICT it does not.  Log below on the system I'm testing on.  The test on the
> system is system boots, sleeps for 30 seconds and then reboots.

> [  270.563197] INFO: rcu_sched detected stalls on CPUs/tasks: { 51} (detected by
> 63, t=217205 jiffies, g=3583, c=3582, q=578)

So the stall is on CPU51, but we do not get a backtrace for CPU51. 

The backtrace trigger is only sent to online cpus. So CPU51 is offline
already. Which makes sense as we are in the process of bringing CPUs
down and the CPUs with backtrace are 0 and 53-63.

I'm pretty sure, that the patch which clears the stale flag is
unrelated to this and it cures the NULL pointer dereference (the
reason why this can happen is clear).

So now you do not longer trip over the NULL pointer dereference, but
you see a weird RCU stall on an already DEAD cpu. Note, it's dead
because we already took CPU52 offline as well.

Paul???

Thanks,

	tglx

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