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=-6.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, 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 BFC7DC04E53 for ; Wed, 15 May 2019 11:13:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9239820862 for ; Wed, 15 May 2019 11:13:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1557918794; bh=NQmfRXX5E4NyWdw6oYf7TSksuQ8l64eBkhFcOl1ifTo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=gnmgPybpNLu+ewdJoFugy+DZ09quR5MAxoe+sMrCK4oofLAyBWe71It+LpNG4/qAE 3xXuVU2sz/TLa4fNpfLM5BNeKQS2rRodXkl2QzySEF06tZ34UD4NSZWE1Ptik8rKNs GhU06K9tlHR2kSuxYQqSrVymyODib76YvWWMG/2o= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729942AbfEOLNN (ORCPT ); Wed, 15 May 2019 07:13:13 -0400 Received: from mail.kernel.org ([198.145.29.99]:48786 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729896AbfEOLNI (ORCPT ); Wed, 15 May 2019 07:13:08 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C567420644; Wed, 15 May 2019 11:13:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1557918788; bh=NQmfRXX5E4NyWdw6oYf7TSksuQ8l64eBkhFcOl1ifTo=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=FFs4fdBUn2Y/MoeHeuo8Fc/HLNwn9Hf8GmBlnjN3ghe0JmBXIYr/dO031q2wzTOoV TZjPcKdP/gVgrQKWcfzg1hTpoe0IofmzR6OuxiJ2VYqvXECDNThb3d73D7xMIQRXeK f6vbTf0HCM0Vkz8LSU5G2iHKszcgry5MRLXceMQ8= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Tyler Hicks , Thomas Gleixner , Ben Hutchings Subject: [PATCH 4.4 251/266] Documentation: Correct the possible MDS sysfs values Date: Wed, 15 May 2019 12:55:58 +0200 Message-Id: <20190515090731.506456823@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190515090722.696531131@linuxfoundation.org> References: <20190515090722.696531131@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Tyler Hicks commit ea01668f9f43021b28b3f4d5ffad50106a1e1301 upstream. Adjust the last two rows in the table that display possible values when MDS mitigation is enabled. They both were slightly innacurate. In addition, convert the table of possible values and their descriptions to a list-table. The simple table format uses the top border of equals signs to determine cell width which resulted in the first column being far too wide in comparison to the second column that contained the majority of the text. Signed-off-by: Tyler Hicks Signed-off-by: Thomas Gleixner [bwh: Backported to 4.4: adjust filename] Signed-off-by: Ben Hutchings Signed-off-by: Greg Kroah-Hartman --- Documentation/hw-vuln/mds.rst | 27 ++++++++++++--------------- 1 file changed, 12 insertions(+), 15 deletions(-) --- a/Documentation/hw-vuln/mds.rst +++ b/Documentation/hw-vuln/mds.rst @@ -95,22 +95,19 @@ mitigations are active. The relevant sys The possible values in this file are: - ========================================= ================================= - 'Not affected' The processor is not vulnerable + .. list-table:: - 'Vulnerable' The processor is vulnerable, - but no mitigation enabled - - 'Vulnerable: Clear CPU buffers attempted' The processor is vulnerable but - microcode is not updated. - The mitigation is enabled on a - best effort basis. - See :ref:`vmwerv` - - 'Mitigation: CPU buffer clear' The processor is vulnerable and the - CPU buffer clearing mitigation is - enabled. - ========================================= ================================= + * - 'Not affected' + - The processor is not vulnerable + * - 'Vulnerable' + - The processor is vulnerable, but no mitigation enabled + * - 'Vulnerable: Clear CPU buffers attempted, no microcode' + - The processor is vulnerable but microcode is not updated. + + The mitigation is enabled on a best effort basis. See :ref:`vmwerv` + * - 'Mitigation: Clear CPU buffers' + - The processor is vulnerable and the CPU buffer clearing mitigation is + enabled. If the processor is vulnerable then the following information is appended to the above information: