queue-4.9/0073-Documentation-Correct-the-possible-MDS-sysfs-values.patch

   1 From 879c8e10e055edc6300a6ffa23324202a333f11a Mon Sep 17 00:00:00 2001
   2 From: Tyler Hicks <tyhicks@canonical.com>
   3 Date: Mon, 6 May 2019 23:52:58 +0000
   4 Subject: [PATCH 73/76] Documentation: Correct the possible MDS sysfs values
   5
   6 commit ea01668f9f43021b28b3f4d5ffad50106a1e1301 upstream.
   7
   8 Adjust the last two rows in the table that display possible values when
   9 MDS mitigation is enabled. They both were slightly innacurate.
  10
  11 In addition, convert the table of possible values and their descriptions
  12 to a list-table. The simple table format uses the top border of equals
  13 signs to determine cell width which resulted in the first column being
  14 far too wide in comparison to the second column that contained the
  15 majority of the text.
  16
  17 Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
  18 Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
  19 [bwh: Backported to 4.9: adjust filename]
  20 Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
  21 Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  22 ---
  23  Documentation/hw-vuln/mds.rst | 29 +++++++++++++----------------
  24  1 file changed, 13 insertions(+), 16 deletions(-)
  25
  26 diff --git a/Documentation/hw-vuln/mds.rst b/Documentation/hw-vuln/mds.rst
  27 index 5e92eca5c0a7..daf6fdac49a3 100644
  28 --- a/Documentation/hw-vuln/mds.rst
  29 +++ b/Documentation/hw-vuln/mds.rst
  30 @@ -95,22 +95,19 @@ mitigations are active. The relevant sysfs file is:
  31
  32  The possible values in this file are:
  33
  34 -  =========================================   =================================
  35 -  'Not affected'                               The processor is not vulnerable
  36 -
  37 -  'Vulnerable'                                 The processor is vulnerable,
  38 -                                               but no mitigation enabled
  39 -
  40 -  'Vulnerable: Clear CPU buffers attempted'    The processor is vulnerable but
  41 -                                               microcode is not updated.
  42 -                                               The mitigation is enabled on a
  43 -                                               best effort basis.
  44 -                                               See :ref:`vmwerv`
  45 -
  46 -  'Mitigation: CPU buffer clear'               The processor is vulnerable and the
  47 -                                               CPU buffer clearing mitigation is
  48 -                                               enabled.
  49 -  =========================================   =================================
  50 +  .. list-table::
  51 +
  52 +     * - 'Not affected'
  53 +       - The processor is not vulnerable
  54 +     * - 'Vulnerable'
  55 +       - The processor is vulnerable, but no mitigation enabled
  56 +     * - 'Vulnerable: Clear CPU buffers attempted, no microcode'
  57 +       - The processor is vulnerable but microcode is not updated.
  58 +
  59 +         The mitigation is enabled on a best effort basis. See :ref:`vmwerv`
  60 +     * - 'Mitigation: Clear CPU buffers'
  61 +       - The processor is vulnerable and the CPU buffer clearing mitigation is
  62 +         enabled.
  63
  64  If the processor is vulnerable then the following information is appended
  65  to the above information:
  66 --
  67 2.21.0
  68