linux-kernel - [RFC PATCH 0/3] ACPI: extlog: Log and trace similarly to GHES

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-next>] [day] [month] [year] [list]

Date: Tue,  7 May 2024 21:02:19 +0200
From: "Fabio M. De Francesco" <fabio.m.de.francesco@...ux.intel.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>,
	Len Brown <lenb@...nel.org>,
	linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Dan Williams <dan.j.williams@...el.com>,
	"Fabio M . De Francesco" <fabio.m.de.francesco@...ux.intel.com>
Subject: [RFC PATCH 0/3] ACPI: extlog: Log and trace similarly to GHES

When Firmware First is enabled, BIOS handles errors first and then it
makes them available to the kernel via the Common Platform Error Record
(CPER) sections (UEFI 2.10 Appendix N). Linux parses the CPER sections
via two similar paths, ELOG and GHES.

Currently, ELOG and GHES show some inconsistencies in how they print to
the kernel log as well as in how they report to userspace via trace
events.

This short series wants to make these two competing path act similarly.

This is an RFC mainly because of patch 3/3 which enables kernel logging
even in precence of userspace monitoring events. I'm not sure if this
behavior is wanted.

Fabio M. De Francesco (3):
  ACPI: extlog: Trace CPER Non-standard Section Body
  ACPI: extlog: Trace PCI Express Error Section
  ACPI: extlog: Make print_extlog_rcd() log unconditionally

 drivers/acpi/acpi_extlog.c | 44 +++++++++++++++++++++++++++++++++-----
 drivers/ras/debugfs.c      |  6 ------
 include/linux/ras.h        |  2 --
 3 files changed, 39 insertions(+), 13 deletions(-)

-- 
2.45.0