linux-kernel - [GIT PULL for v6.10-rc6] edac fixes for kernel 6.11

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: Wed, 26 Jun 2024 11:33:41 +0200
From: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Tony Luck <tony.luck@...el.com>, EDAC Mailing List
 <linux-edac@...r.kernel.org>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Mauro Carvalho Chehab
 <m.chehab@...wei.com>, Shengwei Luo <luoshengwei@...wei.com>, Daniel
 Ferguson <danielf@...amperecomputing.com>, Jose <shiju.jose@...wei.com>,
 Jason Tian <jason@...amperecomputing.com>, Jonathan Cameron
 <jonathan.cameron@...wei.com>, Roberto Sassu <roberto.sassu@...wei.com>
Subject: [GIT PULL for v6.10-rc6] edac fixes for kernel 6.11

Hi Borislav,

Please pull from:
  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-edac tags/edac/v6.10-1

For two patches that fix UEFI 2.6+ implementation of the ARM trace event, 
as the original implementation was incomplete.

The patches on this series was sent at:
	https://lore.kernel.org/all/20240321-b4-arm-ras-error-vendor-info-v5-rc3-v5-0-850f9bfb97a8@os.amperecomputing.com/

I did a couple of changes at the first patch addressing some coding style
issues. At the second patch, I replaced the original description to a proper
one identifying precisely why the patch is needed and what it does.

In summary:
changeset e9279e83ad1f ("trace, ras: add ARM processor error trace event")
was incomplete: it added a trace event that was reporting only some fields
of the CPER record generated for ARM processor from UEFI 2.6 spec.

Those are not enough to actually parse such events on userspace, nor to
take any actions like isolating problematic CPU cores.

The patch was validated with the help of an ARM EINJ code for QEMU:

	https://github.com/mchehab/rasdaemon/wiki/error-injection

I tested the ghes and cper reports both with and without this change,
using different versions of rasdaemon, with and without support for
the extended trace event. Those are a summary of the test results:

- adding more fields to the trace events didn't break userspace API:
  both versions of rasdaemon handled it;

- the rasdaemon patches to handle the new trace report was missing
  a backward-compatibility logic. I fixed already. With that, rasdaemon
  can handle both old and new trace events.

Btw, rasdaemon has gained support for the extended trace since its
version 0.5.8 (released in 2021). I didn't saw any issues there
complain about troubles on it, so either distros used on ARM servers
are using an old version of rasdaemon, or they're carrying on the trace
event changes as well.

Regards,
Mauro

---

The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:

Thanks,
Mauro