Stephen Hemminger wrote:
This only affects reboots. But yes, the cpumask code has bugs. Does
the .config involved select MAXSMP?
Patch does not fix the problem. Not sure if it is KVM only problem.
Look like possible cpumask always equals what ACPI / SMP tables report.
So currently looking into alloc_percpu which may not handle the possible
but never used cpus.
Right, it shouldn't have.
It is x86-64 config and does not have MAXSMP set. It does have NR_CPUS set.
So it's not cpumask. Dare I suggest a bisect?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
--
To unsubscribe from this list: send the line "unsubscribe kernel-testers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
