[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1598501530-45821-1-git-send-email-ashok.raj@intel.com>
Date: Wed, 26 Aug 2020 21:12:10 -0700
From: Ashok Raj <ashok.raj@...el.com>
To: linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Cc: Ashok Raj <ashok.raj@...el.com>,
Sukumar Ghorai <sukumar.ghorai@...el.com>,
Srikanth Nandamuri <srikanth.nandamuri@...el.com>,
Evan Green <evgreen@...omium.org>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, x86@...nel.org,
stable@...r.kernel.org
Subject: [PATCH v3] x86/hotplug: Silence APIC only after all irq's are migrated
There is a race when taking a CPU offline. Current code looks like this:
native_cpu_disable()
{
...
apic_soft_disable();
/*
* Any existing set bits for pending interrupt to
* this CPU are preserved and will be sent via IPI
* to another CPU by fixup_irqs().
*/
cpu_disable_common();
{
....
/*
* Race window happens here. Once local APIC has been
* disabled any new interrupts from the device to
* the old CPU are lost
*/
fixup_irqs(); // Too late to capture anything in IRR.
...
}
}
The fix is to disable the APIC *after* cpu_disable_common().
Testing was done with a USB NIC that provided a source of frequent
interrupts. A script migrated interrupts to a specific CPU and
then took that CPU offline.
Fixes: 60dcaad5736f ("x86/hotplug: Silence APIC and NMI when CPU is dead")
Link: https://lore.kernel.org/lkml/875zdarr4h.fsf@nanos.tec.linutronix.de/
Reported-by: Evan Green <evgreen@...omium.org>
Tested-by: Mathias Nyman <mathias.nyman@...ux.intel.com>
Tested-by: Evan Green <evgreen@...omium.org>
Reviewed-by: Evan Green <evgreen@...omium.org>
Signed-off-by: Ashok Raj <ashok.raj@...el.com>
---
v3:
Fix commit message and comments per Thomas.
https://lore.kernel.org/lkml/87mu2iw86q.fsf@nanos.tec.linutronix.de/
v2:
- Typos and fixes suggested by Randy Dunlap
To: linux-kernel@...r.kernel.org
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Sukumar Ghorai <sukumar.ghorai@...el.com>
Cc: Srikanth Nandamuri <srikanth.nandamuri@...el.com>
Cc: Evan Green <evgreen@...omium.org>
Cc: Mathias Nyman <mathias.nyman@...ux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>
Cc: x86@...nel.org
Cc: stable@...r.kernel.org
---
arch/x86/kernel/smpboot.c | 26 ++++++++++++++++++++------
1 file changed, 20 insertions(+), 6 deletions(-)
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index 27aa04a95702..f5ef689dd62a 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -1594,14 +1594,28 @@ int native_cpu_disable(void)
if (ret)
return ret;
- /*
- * Disable the local APIC. Otherwise IPI broadcasts will reach
- * it. It still responds normally to INIT, NMI, SMI, and SIPI
- * messages.
- */
- apic_soft_disable();
cpu_disable_common();
+ /*
+ * Disable the local APIC. Otherwise IPI broadcasts will reach
+ * it. It still responds normally to INIT, NMI, SMI, and SIPI
+ * messages.
+ *
+ * Disabling the APIC must happen after cpu_disable_common()
+ * which invokes fixup_irqs().
+ *
+ * Disabling the APIC preserves already set bits in IRR, but
+ * an interrupt arriving after disabling the local APIC does not
+ * set the corresponding IRR bit.
+ *
+ * fixup_irqs() scans IRR for set bits so it can raise a not
+ * yet handled interrupt on the new destination CPU via an IPI
+ * but obviously it can't do so for IRR bits which are not set.
+ * IOW, interrupts arriving after disabling the local APIC will
+ * be lost.
+ */
+ apic_soft_disable();
+
return 0;
}
--
2.7.4
Powered by blists - more mailing lists