[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250516165518.125495-5-18255117159@163.com>
Date: Sat, 17 May 2025 00:55:18 +0800
From: Hans Zhang <18255117159@....com>
To: bhelgaas@...gle.com,
tglx@...utronix.de,
kw@...ux.com,
manivannan.sadhasivam@...aro.org,
mahesh@...ux.ibm.com
Cc: oohall@...il.com,
linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org,
Hans Zhang <hans.zhang@...tech.com>
Subject: [PATCH 4/4] PCI/AER: Trigger kernel panic on recovery failure if aer_panic is set
From: Hans Zhang <hans.zhang@...tech.com>
Modify pcie_do_recovery() to panic the system when device recovery fails
and aer_panic is enabled via kernel command-line. This addresses scenarios
where PCIe link errors cause bus hangs requiring forced reboots.
Signed-off-by: Hans Zhang <hans.zhang@...tech.com>
---
drivers/pci/pcie/err.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/pci/pcie/err.c b/drivers/pci/pcie/err.c
index 31090770fffc..f0994f66d462 100644
--- a/drivers/pci/pcie/err.c
+++ b/drivers/pci/pcie/err.c
@@ -271,8 +271,12 @@ pci_ers_result_t pcie_do_recovery(struct pci_dev *dev,
pci_uevent_ers(bridge, PCI_ERS_RESULT_DISCONNECT);
- /* TODO: Should kernel panic here? */
- pci_info(bridge, "device recovery failed\n");
+ if (!pci_aer_panic_enabled())
+ pci_info(bridge, "%s: device recovery failed\n",
+ pci_name(bridge));
+ else
+ panic("Kernel panic: %s: device recovery failed\n",
+ pci_name(bridge));
return status;
}
--
2.25.1
Powered by blists - more mailing lists