Eric W. Biederman wrote:
quoted text
> Having cpu_online_map change during assign_irq_vector can result
> in some really nasty and weird things happening.  The one that
> bit me last time was accessing non existent per cpu memory for non
> existent cpus.
> 
> This locking was removed in a sloppy x86_64 and x86_32 merge patch.
> 
> Guys can we please try and avoid subtly breaking x86 when we are
> merging files together?

Queuing for tip:x86/urgent.

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/