summaryrefslogtreecommitdiff
path: root/arch/ia64/include/uapi/git@git.tavy.me:linux.git
diff options
context:
space:
mode:
authorWilliam Roche <william.roche@oracle.com>2026-03-17 10:38:10 +0000
committerBorislav Petkov (AMD) <bp@alien8.de>2026-03-18 23:02:16 +0100
commit201bc182ad6333468013f1af0719ffe125826b6a (patch)
tree750f274b0d4df8f7b134caacee45a43536539e08 /arch/ia64/include/uapi/git@git.tavy.me:linux.git
parentf338e77383789c0cae23ca3d48adcc5e9e137e3c (diff)
x86/mce/amd: Check SMCA feature bit before accessing SMCA MSRs
People do effort to inject MCEs into guests in order to simulate/test handling of hardware errors. The real use case behind it is testing the handling of SIGBUS which the memory failure code sends to the process. If that process is QEMU, instead of killing the whole guest, the MCE can be injected into the guest kernel so that latter can attempt proper handling and kill the user *process* in the guest, instead, which caused the MCE. The assumption being here that the whole injection flow can supply enough information that the guest kernel can pinpoint the right process. But that's a different topic... Regardless of virtualization or not, access to SMCA-specific registers like MCA_DESTAT should only be done after having checked the smca feature bit. And there are AMD machines like Bulldozer (the one before Zen1) which do support deferred errors but are not SMCA machines. Therefore, properly check the feature bit before accessing related MSRs. [ bp: Rewrite commit message. ] Fixes: 7cb735d7c0cb ("x86/mce: Unify AMD DFR handler with MCA Polling") Signed-off-by: William Roche <william.roche@oracle.com> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de> Reviewed-by: Yazen Ghannam <yazen.ghannam@amd.com> Cc: stable@vger.kernel.org Link: https://lore.kernel.org/r/20260218163025.1316501-1-william.roche@oracle.com
Diffstat (limited to 'arch/ia64/include/uapi/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions