From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 41EB9C2D0C6 for ; Wed, 11 Dec 2019 16:06:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 129A2214D8 for ; Wed, 11 Dec 2019 16:06:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576080419; bh=aKyMsMNNEx7hTMTe5IQjn0dfAiW870QaH1J/pl82W/Y=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=dbWixCVq3Jx2dTtQOCMGlspQ7WBm9b1o6ONWbaZGEb8NH8jv25h227kSv/ziL3gZm HbrPsB5gwu8V41PWZITCxny/2+HdhA0XNmc2z5O1B/Qr8R4gjPJ0o/WI7qJ6pMeF/9 H6x2xeModUFTyeqiMRjKndVpYfjYdIKI0bQXMu0E= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731178AbfLKPMe (ORCPT ); Wed, 11 Dec 2019 10:12:34 -0500 Received: from mail.kernel.org ([198.145.29.99]:34354 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731169AbfLKPMd (ORCPT ); Wed, 11 Dec 2019 10:12:33 -0500 Received: from sasha-vm.mshome.net (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 07C572467E; Wed, 11 Dec 2019 15:12:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1576077152; bh=aKyMsMNNEx7hTMTe5IQjn0dfAiW870QaH1J/pl82W/Y=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=m+n7vhSIyq77XxXLABYWlKqM/w0uCbSKXmLFnvzYijITZfk0T2/OzDCyTN3fJs2I4 McydNMVfRUIHOYzZAaoducHPNG3NidN7Y5DKLZnWLK0TNDpKCcfVBFspI8MDCjj6lm McU/OlhYsFmOlHmTnpoP9+bFGqOmQ5M98rEHcTqs= From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Anthony Steinhauser , Michael Ellerman , Sasha Levin , linuxppc-dev@lists.ozlabs.org Subject: [PATCH AUTOSEL 5.4 039/134] powerpc/security/book3s64: Report L1TF status in sysfs Date: Wed, 11 Dec 2019 10:10:15 -0500 Message-Id: <20191211151150.19073-39-sashal@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20191211151150.19073-1-sashal@kernel.org> References: <20191211151150.19073-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org From: Anthony Steinhauser [ 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 Signed-off-by: Michael Ellerman [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 --- arch/powerpc/kernel/security.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/arch/powerpc/kernel/security.c b/arch/powerpc/kernel/security.c index bd91dceb70105..298a2e3ad6f4c 100644 --- a/arch/powerpc/kernel/security.c +++ b/arch/powerpc/kernel/security.c @@ -168,6 +168,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) -- 2.20.1