From: Breno Leitao <leitao@debian.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
Hanjun Guo <guohanjun@huawei.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shuai Xue <xueshuai@linux.alibaba.com>,
Len Brown <lenb@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <baoquan.he@linux.dev>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Dave Young <ruirui.yang@linux.dev>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
riel@surriel.com, caggio@meta.com, kexec@lists.infradead.org,
Breno Leitao <leitao@debian.org>,
kernel-team@meta.com
Subject: [PATCH 0/2] vmcoreinfo: GHES: track fatal hardware errors
Date: Wed, 17 Jun 2026 06:32:46 -0700 [thread overview]
Message-ID: <20260617-hwerr-v1-0-ff131cd6203c@debian.org> (raw)
Hardware errors reported through APEI/GHES are recorded in the kernel's
hwerr_data array so that crash tooling can tell from the vmcore whether a
hardware error preceded a crash.
This short series improves that path:
* The first patch is just a fix.
* The second adds a HWERR_FATAL bucket that records panic-severity
errors -- the ones most likely to have caused the crash -- when GHES
reports them.
Signed-off-by: Breno Leitao <leitao@debian.org>
---
Breno Leitao (2):
ACPI: APEI: GHES: fix severity namespace in ghes_log_hwerr()
vmcore_info: track fatal hardware errors
drivers/acpi/apei/ghes.c | 7 ++++++-
include/uapi/linux/vmcore.h | 1 +
2 files changed, 7 insertions(+), 1 deletion(-)
---
base-commit: 4fa3f5fabb30bf00d7475d5a33459ea83d639bf9
change-id: 20260617-hwerr-a28d5d66ae87
Best regards,
--
Breno Leitao <leitao@debian.org>
next reply other threads:[~2026-06-17 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 13:32 Breno Leitao [this message]
2026-06-17 13:32 ` [PATCH 1/2] ACPI: APEI: GHES: fix severity namespace in ghes_log_hwerr() Breno Leitao
2026-06-17 13:32 ` [PATCH 2/2] vmcore_info: track fatal hardware errors Breno Leitao
2026-06-29 16:02 ` [PATCH 0/2] vmcoreinfo: GHES: " Breno Leitao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260617-hwerr-v1-0-ff131cd6203c@debian.org \
--to=leitao@debian.org \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=bp@alien8.de \
--cc=caggio@meta.com \
--cc=guohanjun@huawei.com \
--cc=kernel-team@meta.com \
--cc=kexec@lists.infradead.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rafael@kernel.org \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=tony.luck@intel.com \
--cc=xueshuai@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®