tick: Use zalloc_cpumask_var for allocating offstack cpumasks
authorThomas Gleixner <tglx@linutronix.de>
Fri, 3 May 2013 18:22:36 +0000 (20:22 +0200)
committerIngo Molnar <mingo@kernel.org>
Sun, 5 May 2013 09:12:19 +0000 (11:12 +0200)
commitfbd44a607a1a5019bc32c3615cead8c5ee8f89c9
treeeec6e7d971a266352d3f8a9d4e90323b4d6afdfb
parentce857229e0c3adc211944a13a5579ef84fd7b4af
tick: Use zalloc_cpumask_var for allocating offstack cpumasks

commit b352bc1cbc (tick: Convert broadcast cpu bitmaps to
cpumask_var_t) broke CONFIG_CPUMASK_OFFSTACK in a very subtle way.

Instead of allocating the cpumasks with zalloc_cpumask_var it uses
alloc_cpumask_var, so we can get random data there, which of course
confuses the logic completely and causes random failures.

Reported-and-tested-by: Dave Jones <davej@redhat.com>
Reported-and-tested-by: Yinghai Lu <yinghai@kernel.org>
Link: http://lkml.kernel.org/r/alpine.LFD.2.02.1305032015060.2990@ionos
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
kernel/time/tick-broadcast.c