summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorDavid Kaplan <david.kaplan@amd.com>2025-09-15 16:47:05 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-11-02 16:18:03 +0300
commit6561a5b4e3d16ecb917a4335532505c0e03eb396 (patch)
treedccab30cda7dd944c2f5acae44f5498dcf1a609b /scripts/gdb/linux/utils.py
parent28621b2b0a8c8cd5f12399bb124bcb1a5b7f08d1 (diff)
downloadlinux-6561a5b4e3d16ecb917a4335532505c0e03eb396.tar.xz
x86/bugs: Fix reporting of LFENCE retpoline
[ Upstream commit d1cc1baef67ac6c09b74629ca053bf3fb812f7dc ] The LFENCE retpoline mitigation is not secure but the kernel prints inconsistent messages about this fact. The dmesg log says 'Mitigation: LFENCE', implying the system is mitigated. But sysfs reports 'Vulnerable: LFENCE' implying the system (correctly) is not mitigated. Fix this by printing a consistent 'Vulnerable: LFENCE' string everywhere when this mitigation is selected. Signed-off-by: David Kaplan <david.kaplan@amd.com> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de> Link: https://lore.kernel.org/20250915134706.3201818-1-david.kaplan@amd.com Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions