diff options
author | Anton Blanchard | 2012-06-28 19:28:57 +0000 |
---|---|---|
committer | Benjamin Herrenschmidt | 2012-07-02 14:30:11 +1000 |
commit | bc1d7702910c7c7e88eb60b58429dbfe293683ce (patch) | |
tree | f71a89900b723af1208bd73e3c330d806fe6a504 /mm | |
parent | bc6dc752f35488160ffac07ae91bed1bddaea32a (diff) |
powerpc/xmon: Use cpumask iterator to avoid warning
We have a bug report where the kernel hits a warning in the cpumask
code:
WARNING: at include/linux/cpumask.h:107
Which is:
WARN_ON_ONCE(cpu >= nr_cpumask_bits);
The backtrace is:
cpu_cmd
cmds
xmon_core
xmon
die
xmon is iterating through 0 to NR_CPUS. I'm not sure why we are still
open coding this but iterating above nr_cpu_ids is definitely a bug.
This patch iterates through all possible cpus, in case we issue a
system reset and CPUs in an offline state call in.
Perhaps the old code was trying to handle CPUs that were in the
partition but were never started (eg kexec into a kernel with an
nr_cpus= boot option). They are going to die way before we get into
xmon since we haven't set any kernel state up for them.
Signed-off-by: Anton Blanchard <anton@samba.org>
CC: <stable@kernel.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions