linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: asteinhauser@google.com
To: benh@kernel.crashing.org, paulus@samba.org, diana.craciun@nxp.com
Cc: linuxppc-dev@lists.ozlabs.org,
	Anthony Steinhauser <asteinhauser@google.com>
Subject: [PATCH] L1TF support in PowerPC SYSFS.
Date: Tue, 29 Oct 2019 12:07:59 -0700	[thread overview]
Message-ID: <20191029190759.84821-1-asteinhauser@google.com> (raw)

From: Anthony Steinhauser <asteinhauser@google.com>

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.
https://www.ibm.com/blogs/psirt/potential-impact-processors-power-family/
https://github.com/google/safeside/pull/52
Signed-off-by: Anthony Steinhauser <asteinhauser@google.com>
---
 arch/powerpc/kernel/security.c | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/arch/powerpc/kernel/security.c b/arch/powerpc/kernel/security.c
index 7cfcb294b11c..a1a5017c5170 100644
--- a/arch/powerpc/kernel/security.c
+++ b/arch/powerpc/kernel/security.c
@@ -135,7 +135,8 @@ void setup_spectre_v2(void)
 #endif /* CONFIG_PPC_FSL_BOOK3E */
 
 #ifdef CONFIG_PPC_BOOK3S_64
-ssize_t cpu_show_meltdown(struct device *dev, struct device_attribute *attr, char *buf)
+static ssize_t cpu_show_delayed_fault_common(
+		struct device *dev, struct device_attribute *attr, char *buf)
 {
 	bool thread_priv;
 
@@ -167,6 +168,16 @@ 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_delayed_fault_common(dev, attr, buf);
+}
+
+ssize_t cpu_show_meltdown(struct device *dev, struct device_attribute *attr, char *buf)
+{
+	return cpu_show_delayed_fault_common(dev, attr, buf);
+}
 #endif
 
 ssize_t cpu_show_spectre_v1(struct device *dev, struct device_attribute *attr, char *buf)
-- 
2.24.0.rc0.303.g954a862665-goog


             reply	other threads:[~2019-10-29 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 19:07 asteinhauser [this message]
2019-11-02 11:11 ` [PATCH] L1TF support in PowerPC SYSFS Michael Ellerman
2019-11-04 10:28   ` Anthony Steinhauser
2019-11-14  9:08 ` Michael Ellerman

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=20191029190759.84821-1-asteinhauser@google.com \
    --to=asteinhauser@google.com \
    --cc=benh@kernel.crashing.org \
    --cc=diana.craciun@nxp.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    /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;
as well as URLs for NNTP newsgroup(s).