From: Will Deacon <will@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, James Morse <james.morse@arm.com>,
Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
Robert Moore <robert.moore@intel.com>,
Breno Leitao <leitao@debian.org>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
acpica-devel@lists.linux.dev, kernel-team@meta.com
Subject: Re: [PATCH v2] arm64: Mark kernel as tainted on SAE and SError panic
Date: Thu, 17 Jul 2025 11:46:18 +0100 [thread overview]
Message-ID: <175274683701.735514.4319542940682343455.b4-ty@kernel.org> (raw)
In-Reply-To: <20250716-vmcore_hw_error-v2-1-f187f7d62aba@debian.org>
On Wed, 16 Jul 2025 02:42:01 -0700, Breno Leitao wrote:
> Set TAINT_MACHINE_CHECK when SError or Synchronous External Abort (SEA)
> interrupts trigger a panic to flag potential hardware faults. This
> tainting mechanism aids in debugging and enables correlation of
> hardware-related crashes in large-scale deployments.
>
> This change aligns with similar patches[1] that mark machine check
> events when the system crashes due to hardware errors.
>
> [...]
Applied to arm64 (for-next/misc), thanks!
[1/1] arm64: Mark kernel as tainted on SAE and SError panic
https://git.kernel.org/arm64/c/d7ce7e3a8464
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2025-07-17 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 9:42 [PATCH v2] arm64: Mark kernel as tainted on SAE and SError panic Breno Leitao
2025-07-16 10:19 ` Mark Rutland
2025-07-16 10:52 ` Breno Leitao
2025-07-17 9:57 ` Will Deacon
2025-07-17 10:46 ` Will Deacon [this message]
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=175274683701.735514.4319542940682343455.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=acpica-devel@lists.linux.dev \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=tony.luck@intel.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