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

Hi,
On Tue, 2005-04-26 at 12:25, Zwane Mwaikambo 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?
I'm not sure if other routines using broadcast IPI have this bug. Fixing
the send_ipi_all API looks more generic. Is there any reason we should
use broadcast IPI?

Thanks,
Shaohua

-
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: Zwane Mwaikambo <[email protected]>

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

• Prev by Date: Re: [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!)
• Next by Date: Re: [PATCH] PCI: Add pci shutdown ability
• Previous by thread: Re: [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]