Re: BUG_ON(!cpus_equal(cpumask, tmp));

From: Andrew Morton
Date: Tue Mar 30 2004 - 20:10:02 EST

"Martin J. Bligh" <mbligh@xxxxxxxxxxx> wrote:
> I made a similar patch, but I don't see how we can really fix it without
> providing locking on cpu_online_map.

Are we missing something here?

Why does, for example, smp_send_reschedule() not have the same problem?
Because we've gone around and correctly removed all references to the CPU
from the scheduler data structures before offlining it.

But we're not doing that in the mm code, right? Should we not be taking
mmlist_lock and running around knocking this CPU out of everyone's
cpu_vm_mask before offlining it?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at