diff options
author | Rusty Russell <rusty@rustcorp.com.au> | 2009-04-21 16:03:41 +0930 |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2009-04-21 10:09:50 +0200 |
commit | fcc5c4a2feea3886dc058498b28508b2731720d5 (patch) | |
tree | 10aa7e61b47ab242c25f52714640b324f69520ff /arch/x86 | |
parent | 2f537a9f8e82f55c241b002c8cfbf34303b45ada (diff) | |
download | linux-3.10-fcc5c4a2feea3886dc058498b28508b2731720d5.tar.gz linux-3.10-fcc5c4a2feea3886dc058498b28508b2731720d5.tar.bz2 linux-3.10-fcc5c4a2feea3886dc058498b28508b2731720d5.zip |
x86: avoid theoretical spurious NMI backtraces with CONFIG_CPUMASK_OFFSTACK=y
In theory (though not shown in practice) alloc_cpumask_var() doesn't zero
memory, so CPUs might print an "NMI backtrace for cpu %d" once on boot.
(Bug introduced in fcef8576d8a64fc603e719c97d423f9f6d4e0e8b).
[ Impact: avoid theoretical syslog noise in rare configs ]
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: Steven Rostedt <rostedt@goodmis.org>
LKML-Reference: <alpine.DEB.2.00.0904202113520.10097@gandalf.stny.rr.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'arch/x86')
-rw-r--r-- | arch/x86/kernel/apic/nmi.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/kernel/apic/nmi.c b/arch/x86/kernel/apic/nmi.c index 2ba52f35a88..ce4fbfa315a 100644 --- a/arch/x86/kernel/apic/nmi.c +++ b/arch/x86/kernel/apic/nmi.c @@ -138,7 +138,7 @@ int __init check_nmi_watchdog(void) if (!prev_nmi_count) goto error; - alloc_cpumask_var(&backtrace_mask, GFP_KERNEL); + alloc_cpumask_var(&backtrace_mask, GFP_KERNEL|__GFP_ZERO); printk(KERN_INFO "Testing NMI watchdog ... "); #ifdef CONFIG_SMP |