PCI: PCIe: PME: Fix pcie_pme_remove()
PATCH 1/1 PCI: PCIe: PME: Fix pcie_pme_remove()
From: Rafael J. Wysocki <[email protected]>
It is incorrect to call pcie_pme_suspend() from pcie_pme_remove() for two reasons.
First, pcie_pme_suspend() calls synchronize_irq() that will wait for the native hotplug interrupt handler as well as for the PME one, because they share one IRQ (as per the spec). That may deadlock if hotplug is signaled while pcie_pme_remove() is running and the latter calls pci_lock_rescan_remove() before the former.
Second, if pcie_pme_suspend() figures out that wakeup needs to be enabled for the port, it will return without disabling the interrupt as expected by pcie_pme_remove() which was overlooked by commit c7b5a4e6e8fb ("PCI / PM: Fix native PME handling during system suspend/resume").
To fix that, rework pcie_pme_remove() to disable the PME interrupt, clear its status and prevent the PME worker function from re-enabling it before calling free_irq() on it which should be sufficient.
--- drivers/pci/pcie/pme.c | 22 +++++++++++++++------- 1 file changed, 15 insertions(+), 7 deletions(-)
drivers/pci/pcie/pme.c +15 -7
@@ -363,6 +363,16 @@ static bool pcie_pme_check_wakeup(structreturn false; } +static void pcie_pme_disable_interrupt (struct pci_dev *port, +struct pcie_pme_service_data *data) +{ +spin_lock_irq (&data->lock); +pcie_pme_interrupt_enable (port, false); +pcie_clear_root_pme_status (port); + data->noirq = true; +spin_unlock_irq (&data->lock); +} +/** * pcie_pme_suspend - Suspend PCIe PME service device. * @srv: PCIe service device to suspend.
@@ -387,11 +397,7 @@ static int pcie_pme_suspend(struct pcie_return 0 ; } -spin_lock_irq (&data->lock); -pcie_pme_interrupt_enable (port, false); -pcie_clear_root_pme_status (port); - data->noirq = true; -spin_unlock_irq (&data->lock); +pcie_pme_disable_interrupt (port, data);synchronize_irq (srv->irq);
@@ -427,9 +433,11 @@ static int pcie_pme_resume(struct pcie_d*/ static void pcie_pme_remove (struct pcie_device *srv) { -pcie_pme_suspend (srv); +struct pcie_pme_service_data *data =get_service_data (srv); + +pcie_pme_disable_interrupt (srv->port, data);free_irq (srv->irq, srv); -kfree (get_service_data (srv)); +kfree (data); }static int pcie_pme_runtime_suspend (struct pcie_device *srv)
Bjorn Helgaas
maintainerQuoted 18 lines · Rafael J. Wysocki
From: Rafael J. Wysocki <[email protected]>
It is incorrect to call
pcie_pme_suspend()frompcie_pme_remove()for two reasons.First,
pcie_pme_suspend()callssynchronize_irq()that will wait for the native hotplug interrupt handler as well as for the PME one, because they share one IRQ (as per the spec). That may deadlock if hotplug is signaled whilepcie_pme_remove()is running and the latter callspci_lock_rescan_remove()before the former.Second, if
pcie_pme_suspend()figures out that wakeup needs to be enabled for the port, it will return without disabling the interrupt as expected bypcie_pme_remove()which was overlooked by commitc7b5a4e6e8fb("PCI / PM: Fix native PME handling during system suspend/resume").
Quoted 7 lines
To fix that, rework
pcie_pme_remove()to disable the PME interrupt, clear its status and prevent the PME worker function from re-enabling it before callingfree_irq()on it which should be sufficient.Fixes c7b5a4e6e8fb ("PCI / PM: Fix native PME handling during system suspend/resume")Reported-by Dongdong Liu <[email protected]>Signed-off-by Rafael J. Wysocki <[email protected]>
I added the deadlock details from Dongdong and applied this to pci/pm for v5.1, thanks!
Bjorn