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]

Date:	Fri, 28 Jun 2013 12:52:02 +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>
Subject: Re: BUG: tick device NULL pointer during system initialization and
 shutdown

On Thu, 27 Jun 2013, Prarit Bhargava wrote:
> On 06/26/2013 07:05 AM, Thomas Gleixner wrote:
> > Subject: tick: Make oneshot broadcast robust vs. CPU offlining
> > From: Thomas Gleixner <tglx@...utronix.de>
> > Date: Wed, 26 Jun 2013 12:17:32 +0200
> > 
> > In periodic mode we remove offline cpus from the broadcast propagation
> > mask. In oneshot mode we fail to do so. This was not a problem so far,
> > but the recent changes to the broadcast propagation introduced a
> > constellation which can result in a NULL pointer dereference.
> > 
> 
> Unfortunately this patch causes an NMI watchdog during system shutdown.  Most of
> the CPUs are in start_secondary+0x254/0x256.

Huch. Did the warning in the broadcast code trigger before that?
 
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/