linux-kernel - Re: [PATCH 2/3 v4] ACPI: extlog: Trace CPER PCI Express Error Section

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250701135855.00004406@huawei.com>
Date: Tue, 1 Jul 2025 13:58:55 +0100
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: "Fabio M. De Francesco" <fabio.m.de.francesco@...ux.intel.com>
CC: <linux-cxl@...r.kernel.org>, "Rafael J . Wysocki" <rafael@...nel.org>,
	"Len Brown" <lenb@...nel.org>, Davidlohr Bueso <dave@...olabs.net>, Dave
 Jiang <dave.jiang@...el.com>, Alison Schofield <alison.schofield@...el.com>,
	Vishal Verma <vishal.l.verma@...el.com>, Ira Weiny <ira.weiny@...el.com>, Dan
 Williams <dan.j.williams@...el.com>, Mahesh J Salgaonkar
	<mahesh@...ux.ibm.com>, Oliver O'Halloran <oohall@...il.com>, Bjorn Helgaas
	<bhelgaas@...gle.com>, Tony Luck <tony.luck@...el.com>, Borislav Petkov
	<bp@...en8.de>, <linux-acpi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<linuxppc-dev@...ts.ozlabs.org>, <linux-pci@...r.kernel.org>,
	<linux-edac@...r.kernel.org>
Subject: Re: [PATCH 2/3 v4] ACPI: extlog: Trace CPER PCI Express Error
 Section

On Mon, 23 Jun 2025 16:54:19 +0200
"Fabio M. De Francesco" <fabio.m.de.francesco@...ux.intel.com> wrote:

> I/O Machine Check Architecture events may signal failing PCIe components
> or links. The AER event contains details on what was happening on the wire
> when the error was signaled.
> 
> Trace the CPER PCIe Error section (UEFI v2.10, Appendix N.2.7) reported
> by the I/O MCA.
> 
> Cc: Dan Williams <dan.j.williams@...el.com>
> Reviewed-by: Dave Jiang <dave.jiang@...el.com>
> Signed-off-by: Fabio M. De Francesco <fabio.m.de.francesco@...ux.intel.com>
Reviewed-by: Jonathan Cameron <jonathan.cameron@...wei.com>