linux-kernel - [PATCH] Documentation: Use list table for possible GDS sysfs values

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240903132533.26458-1-itazur@amazon.com>
Date: Tue, 3 Sep 2024 13:25:33 +0000
From: Takahiro Itazuri <itazur@...zon.com>
To: <linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC: Takahiro Itazuri <itazur@...zon.com>, Takahiro Itazuri
	<zulinx86@...il.com>, Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov
	<bp@...en8.de>, Peter Zijlstra <peterz@...radead.org>, Josh Poimboeuf
	<jpoimboe@...nel.org>, Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
	Jonathan Corbet <corbet@....net>
Subject: [PATCH] Documentation: Use list table for possible GDS sysfs values

Using a normal table, a line break in the first column would be
recognized as two rows. Uses a list table instead as in MDS.

Signed-off-by: Takahiro Itazuri <itazur@...zon.com>
---
 .../hw-vuln/gather_data_sampling.rst          | 36 ++++++++++---------
 1 file changed, 19 insertions(+), 17 deletions(-)

diff --git a/Documentation/admin-guide/hw-vuln/gather_data_sampling.rst b/Documentation/admin-guide/hw-vuln/gather_data_sampling.rst
index 264bfa937f7d..4a2eaa80d20a 100644
--- a/Documentation/admin-guide/hw-vuln/gather_data_sampling.rst
+++ b/Documentation/admin-guide/hw-vuln/gather_data_sampling.rst
@@ -85,23 +85,25 @@ GDS this can be accessed by the following sysfs file:
 
 The possible values contained in this file are:
 
- ============================== =============================================
- Not affected                   Processor not vulnerable.
- Vulnerable                     Processor vulnerable and mitigation disabled.
- Vulnerable: No microcode       Processor vulnerable and microcode is missing
-                                mitigation.
- Mitigation: AVX disabled,
- no microcode                   Processor is vulnerable and microcode is missing
-                                mitigation. AVX disabled as mitigation.
- Mitigation: Microcode          Processor is vulnerable and mitigation is in
-                                effect.
- Mitigation: Microcode (locked) Processor is vulnerable and mitigation is in
-                                effect and cannot be disabled.
- Unknown: Dependent on
- hypervisor status              Running on a virtual guest processor that is
-                                affected but with no way to know if host
-                                processor is mitigated or vulnerable.
- ============================== =============================================
+  .. list-table::
+
+     * - 'Not affected'
+       - Processor is not vulnerable.
+     * - 'Vulnerable'
+       - Processor is vulnerable and mitigation is disabled.
+     * - 'Vulnerable: No microcode'
+       - Processor is vulnerable and microcode is missing mitigation.
+     * - 'Mitigation: AVX disabled, no microcode'
+       - Processor is vulnerable and microcode is missing mitigation. AVX
+         disabled as mitigation.
+     * - 'Mitigation: Microcode'
+       - Processor is vulnerable and mitigation is in effect.
+     * - 'Mitigation: Microcode (locked)'
+       - Processor is vulnerable and mitigation is in effect and cannot be
+         disabled.
+     * - 'Unknown: Dependent on hypervisor status'
+       - Running on a virtual guest processor that is affected but with no way
+         to know if host processor is mitigated or vulnerable.
 
 GDS Default mitigation
 ----------------------
-- 
2.40.1