On Sat, 2025-10-25 at 11:58 -0400, Sasha Levin wrote:
From: Kai Huang kai.huang@intel.com
[ Upstream commit b18651f70ce0e45d52b9e66d9065b831b3f30784 ]
[...]
LLM Generated explanations, may be completely bogus:
YES
**Why This Fix Matters**
- Prevents machine checks during kexec/kdump on early TDX-capable platforms with the “partial write to TDX private memory” erratum. Without this, the new kernel may hit an MCE after the old kernel jumps, which is a hard failure affecting users.
Hi,
I don't think we should backport this for 6.17 stable. Kexec/kdump and TDX are mutually exclusive in Kconfig in 6.17, therefore it's not possible for TDX to impact kexec/kdump.
This patch is part of the series which enables kexec/kdump together with TDX in Kconfig (which landed in 6.18) and should not be backported alone.