summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorAnthony Steinhauser <asteinhauser@google.com>2019-10-29 22:07:59 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-01-04 15:34:27 +0300
commit43d8ff8f09f027275dbee75df6d78487e0335d2a (patch)
treef0468a3b0b7285ffe4a0f5e0d60ffbaa1f2f2dcc /arch
parentd0eba4f1059ca1b99ad2e8eded69d7b3bb0e8116 (diff)
downloadlinux-43d8ff8f09f027275dbee75df6d78487e0335d2a.tar.xz
powerpc/security/book3s64: Report L1TF status in sysfs
[ Upstream commit 8e6b6da91ac9b9ec5a925b6cb13f287a54bd547d ] Some PowerPC CPUs are vulnerable to L1TF to the same extent as to Meltdown. It is also mitigated by flushing the L1D on privilege transition. Currently the sysfs gives a false negative on L1TF on CPUs that I verified to be vulnerable, a Power9 Talos II Boston 004e 1202, PowerNV T2P9D01. Signed-off-by: Anthony Steinhauser <asteinhauser@google.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> [mpe: Just have cpu_show_l1tf() call cpu_show_meltdown() directly] Link: https://lore.kernel.org/r/20191029190759.84821-1-asteinhauser@google.com Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/powerpc/kernel/security.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/arch/powerpc/kernel/security.c b/arch/powerpc/kernel/security.c
index 156cfe6d23b0..fc5c49046aa7 100644
--- a/arch/powerpc/kernel/security.c
+++ b/arch/powerpc/kernel/security.c
@@ -161,6 +161,11 @@ ssize_t cpu_show_meltdown(struct device *dev, struct device_attribute *attr, cha
return sprintf(buf, "Vulnerable\n");
}
+
+ssize_t cpu_show_l1tf(struct device *dev, struct device_attribute *attr, char *buf)
+{
+ return cpu_show_meltdown(dev, attr, buf);
+}
#endif
ssize_t cpu_show_spectre_v1(struct device *dev, struct device_attribute *attr, char *buf)