Re: [PATCH]broadcast IPI race condition on CPU hotplug

Hi Shaohua,

On Tue, 26 Apr 2005, Li Shaohua wrote:

> After a CPU is booted but before it's officially up (set online map, and
> enable interrupt), the CPU possibly will receive a broadcast IPI. After
> it's up, it will handle the stale interrupt soon and maybe cause oops if
> it's a smp-call-function-interrupt. This is quite possible in CPU
> hotplug case, but nearly can't occur at boot time. Below patch replaces
> broadcast IPI with send_ipi_mask just like the cluster mode.

Ok, but isn't it sufficient to use send_ipi_mask in smp_call_function 
instead?

Thanks,
	Zwane
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH]broadcast IPI race condition on CPU hotplug
    • From: Li Shaohua <[email protected]>

• References:
  • [PATCH]broadcast IPI race condition on CPU hotplug
    • From: Li Shaohua <[email protected]>

• Prev by Date: Re: Mercurial 0.3 vs git benchmarks
• Next by Date: Re: Mercurial 0.3 vs git benchmarks
• Previous by thread: [PATCH]broadcast IPI race condition on CPU hotplug
• Next by thread: Re: [PATCH]broadcast IPI race condition on CPU hotplug
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]