PCI hotplug driver fixes
v4 cover PCI hotplug driver fixes
The fix of Powerpc hotplug driver (drivers/pci/hotplug/pnv_php.c) addresses below two issues.
1. Kernel Crash during hot unplug of bridge/switch slot.
2. Bridge Support Enablement - Previously, when we do a hot-unplug operation on a bridge slot, all the ports and devices behind the bridge-ports would be hot-unplugged/offline, but when we do a hot-plug operation on the same bridge slot, all the ports and devices behind the bridge would not get hot-plugged/online. In this case, Only the first port of the bridge gets enabled and the remaining port/devices remain unplugged/offline. After the fix, The hot-unplug and hot-plug operations on the slot associated with the bridge started behaving correctly and became in sync. Now, after the hot plug operation on the same slot, all the bridge ports and devices behind the bridge become hot-plugged/online/restored in the same manner as it was before the hot-unplug operation.
Krishna Kumar (2):
pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv
powerpc: hotplug driver bridge support
arch/powerpc/include/asm/ppc-pci.h | 4 ++++ arch/powerpc/kernel/pci-hotplug.c | 5 ++--- arch/powerpc/kernel/pci_dn.c | 32 ++++++++++++++++++++++++++++++ drivers/pci/hotplug/pnv_php.c | 3 +-- 4 files changed, 39 insertions(+), 5 deletions(-)
Changelog:
==========
v4: 1st July 2024
- Changed the description and corrected the typo in patch1
- Added Acked-by and Tested-by tag in patch1
- Added Tested-by tag in patch2
v3: 24 June 2024
- Removed the DPC keyword from description in cover letter and patch2
v2: 14 May 2024
- Used of_property_read_u32() in place of of_get_property() and
of_read_number(). [patch2]
- Removed some unnecessary variable and changed the function return type from void* to void. [patch2]
- Removed the export declaration of pci_traverse_sibling_nodes_and_scan_slot() as its not needed. [patch2]
Signature · 1 line
2.45.0
PATCH v4 1/2 pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv
Description of the problem: The hotplug driver for powerpc (pci/hotplug/pnv_php.c) gives kernel crash when we try to hot-unplug/disable the PCIe switch/bridge from the PHB.
Root Cause of Crash: The crash is due to the reason that, though the msi data structure has been released during disable/hot-unplug path and it has been assigned with NULL, still during unregistration the code was again trying to explicitly disable the MSI which causes the NULL pointer dereference and kernel crash.
The patch fixes the check during unregistration path to prevent invoking pci_disable_msi/msix() since its data structure is already freed.
--- drivers/pci/hotplug/pnv_php.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/pci/hotplug/pnv_php.c +1 -2
@@ -40,7 +40,6 @@ static void pnv_php_disable_irq(struct pnv_php_slot *php_slot, bool disable_device) {struct pci_dev *pdev = php_slot->pdev; -int irq = php_slot->irq;u16 ctrl;if (php_slot->irq >0 ) {
@@ -59,7 +58,7 @@ static void pnv_php_disable_irq(struct pnv_php_slot *php_slot, php_slot->wq =NULL ; } -if (disable_device || irq >0 ) { +if (disable_device) {if (pdev->msix_enabled)pci_disable_msix (pdev);else if (pdev->msi_enabled)
Signature · 1 line
2.45.0
Re: [PATCH v4 1/2] pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv
Hi Michael,
When you apply/merge the patch, please consider below URL in commit message. This is the URL where this issue was reported -
https://lists.ozlabs.org/pipermail/linuxppc-dev/2023-December/267034.html
Thanks,
Krishna
Quoted 50 lines · Krishna Kumar
Description of the problem: The hotplug driver for powerpc (
pci/hotplug/pnv_php.c) gives kernel crash when we try to hot-unplug/disable the PCIe switch/bridge from the PHB.Root Cause of Crash: The crash is due to the reason that, though the msi data structure has been released during disable/hot-unplug path and it has been assigned with NULL, still during unregistration the code was again trying to explicitly disable the MSI which causes the NULL pointer dereference and kernel crash.
The patch fixes the check during unregistration path to prevent invoking pci_disable_msi/msix() since its data structure is already freed.
Cc Michael Ellerman <[email protected]>Cc Nicholas Piggin <[email protected]>Cc Christophe Leroy <[email protected]>Cc "Aneesh Kumar K.V" <[email protected]>Cc Bjorn Helgaas <[email protected]>Cc Gaurav Batra <[email protected]>Cc Nathan Lynch <[email protected]>Cc Brian King <[email protected]>Acked-by Bjorn Helgaas <[email protected]>Tested-by Shawn Anastasio <[email protected]>Signed-off-by Krishna Kumar <[email protected]>--- drivers/pci/hotplug/pnv_php.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)drivers/pci/hotplug/pnv_php.c +1
-2@@ -40,7 +40,6 @@ static void pnv_php_disable_irq(struct pnv_php_slot *php_slot, bool disable_device) {struct pci_dev *pdev = php_slot->pdev; -int irq = php_slot->irq;u16 ctrl;if (php_slot->irq >0 ) {@@ -59,7 +58,7 @@ static void pnv_php_disable_irq(struct pnv_php_slot *php_slot, php_slot->wq =NULL ; } -if (disable_device || irq >0 ) { +if (disable_device) {if (pdev->msix_enabled)pci_disable_msix (pdev);else if (pdev->msi_enabled)
PATCH v4 2/2 powerpc: hotplug driver bridge support
In reply to Krishna KumarThere is an issue with the hotplug operation when it's done on the bridge/switch slot. The bridge-port and devices behind the bridge, which become offline by hot-unplug operation, don't get hot-plugged/enabled by doing hot-plug operation on that slot. Only the first port of the bridge gets enabled and the remaining port/devices remain unplugged. The hot plug/unplug operation is done by the hotplug driver (drivers/pci/hotplug/pnv_php.c).
Root Cause Analysis: This behavior is due to missing code for the switch/bridge. The existing driver depends on pci_hp_add_devices() function for device enablement. This function calls pci_scan_slot() on only one device-node/port of the bridge, not on all the siblings' device-node/port.
The missing code needs to be added which will find all the sibling device-nodes/bridge-ports and will run explicit pci_scan_slot() on those. A new function has been added for this purpose which gets invoked from pci_hp_add_devices(). This new function pci_traverse_sibling_nodes_and_scan_slot() gets all the sibling bridge-ports by traversal and explicitly invokes pci_scan_slot on them.
--- arch/powerpc/include/asm/ppc-pci.h | 4 ++++ arch/powerpc/kernel/pci-hotplug.c | 5 ++--- arch/powerpc/kernel/pci_dn.c | 32 ++++++++++++++++++++++++++++++ 3 files changed, 38 insertions(+), 3 deletions(-)
arch/powerpc/include/asm/ppc-pci.h +4 -0
@@ -28,6 +28,10 @@ struct pci_dn;void *pci_traverse_device_nodes (struct device_node *start,void *(*fn)(struct device_node *,void *),void *data); + +void pci_traverse_sibling_nodes_and_scan_slot (struct device_node *start, +struct pci_bus *bus); +extern void pci_devs_phb_init_dynamic (struct pci_controller *phb); #if defined(CONFIG_IOMMU_API) && (defined(CONFIG_PPC_PSERIES) || \
arch/powerpc/kernel/pci-hotplug.c +2 -3
@@ -106,7 +106,7 @@ EXPORT_SYMBOL_GPL(pci_hp_remove_devices);*/ void pci_hp_add_devices (struct pci_bus *bus) { -int slotno, mode, max; +int mode, max;struct pci_dev *dev;struct pci_controller *phb;struct device_node *dn =pci_bus_to_OF_node (bus);
@@ -129,8 +129,7 @@ void pci_hp_add_devices(struct pci_bus *bus)* order for fully rescan all the way down to pick them up. * They can have been removed during partial hotplug. */ - slotno =PCI_SLOT (PCI_DN (dn->child)->devfn); -pci_scan_slot (bus,PCI_DEVFN (slotno,0 )); +pci_traverse_sibling_nodes_and_scan_slot (dn, bus); max = bus->busn_res.start;/* * Scan bridges that are already configured. We don't touch
arch/powerpc/kernel/pci_dn.c +32 -0
@@ -493,4 +493,36 @@ static void pci_dev_pdn_setup(struct pci_dev *pdev) pdn =pci_get_pdn (pdev); pdev->dev.archdata.pci_data = pdn; } + +void pci_traverse_sibling_nodes_and_scan_slot (struct device_node *start,struct pci_bus *bus) +{ +struct device_node *dn; +int slotno; + +u32 class =0 ; + +if (!of_property_read_u32 (start->child,"class-code" , &class)) { +/* Call of pci_scan_slot for non-bridge/EP case */ +if (!((class >>8 ) ==PCI_CLASS_BRIDGE_PCI )) { + slotno =PCI_SLOT (PCI_DN (start->child)->devfn); +pci_scan_slot (bus,PCI_DEVFN (slotno,0 )); +return ; + } + } + +/* Iterate all siblings */ +for_each_child_of_node (start, dn) { + class =0 ; + +if (!of_property_read_u32 (start->child,"class-code" , &class)) { +/* Call of pci_scan_slot on each sibling-nodes/bridge-ports */ +if ((class >>8 ) ==PCI_CLASS_BRIDGE_PCI ) { + slotno =PCI_SLOT (PCI_DN (dn)->devfn); +pci_scan_slot (bus,PCI_DEVFN (slotno,0 )); + } + } + } + +} +DECLARE_PCI_FIXUP_EARLY (PCI_ANY_ID ,PCI_ANY_ID , pci_dev_pdn_setup);
Signature · 1 line
2.45.0
Michael Ellerman
AppliedQuoted 18 lines · Krishna Kumar
The fix of Powerpc hotplug driver (
drivers/pci/hotplug/pnv_php.c) addresses below two issues.1. Kernel Crash during hot unplug of bridge/switch slot.
2. Bridge Support Enablement - Previously, when we do a hot-unplug operation on a bridge slot, all the ports and devices behind the bridge-ports would be hot-unplugged/offline, but when we do a hot-plug operation on the same bridge slot, all the ports and devices behind the bridge would not get hot-plugged/online. In this case, Only the first port of the bridge gets enabled and the remaining port/devices remain unplugged/offline. After the fix, The hot-unplug and hot-plug operations on the slot associated with the bridge started behaving correctly and became in sync. Now, after the hot plug operation on the same slot, all the bridge ports and devices behind the bridge become hot-plugged/online/restored in the same manner as it was before the hot-unplug operation.
Quoted 1 line
[...]
Applied to powerpc/next.
[1/2] pci/hotplug/pnv_php: Fix hotplug driver crash on Powernv
https://git.kernel.org/powerpc/c/335e35b748527f0c06ded9eebb65387f60647fda [2/2] powerpc: hotplug driver bridge support https://git.kernel.org/powerpc/c/20ce0c247b2500cb7060cb115274ba71abda2626
cheers