lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 28 May 2013 12:48:46 -0600 From: Betty Dall <betty.dall@...com> To: rjw@...k.pl, bhelgaas@...gle.com Cc: ying.huang@...el.com, linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, Betty Dall <betty.dall@...com> Subject: [PATCH 0/3] PCI/ACPI: Fix firmware first error recovery with root port in reset This patch set fixes a bug on platforms that use firmware first AER. Firmware can leave the root port in Secondary Bus Reset (SBR) and communicate this to the OS through the "reset" bit in the flags field of the HEST table and associated CPER records. Firmware wants to do this so that the error is contained and the hardware is in a known state. Without these patches, the root port stays in SBR and the device drivers cannot recover. These patches recognize when the firmware first root port is in SBR and bring the root port out of SBR so the devices under the root port can recover. The changes have been tested on systems with firmware first that set the "reset" bit by injecting various hardware errors. The errors successfully recover. --- Betty Dall (3): PCI/AER: Fix incorrect return from aer_hest_parse() ACPI/APEI: Force fatal AER severity when bus has been reset PCI/AER: Provide reset_link for firmware first root port --- drivers/acpi/apei/ghes.c | 21 ++++++++++++++++++- drivers/pci/pcie/aer/aerdrv_acpi.c | 3 ++ drivers/pci/pcie/aer/aerdrv_core.c | 38 ++++++++++++++++++++++++++++++++++++ 3 files changed, 61 insertions(+), 1 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists