Documentation: Move L1TF to separate directory

Move L!TF to a separate directory so the MDS stuff can be added at the
side. Otherwise the all hardware vulnerabilites have their own top level
entry. Should have done that right away.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: Jon Masters <jcm@redhat.com>
This commit is contained in:
Thomas Gleixner 2019-02-19 11:10:49 +01:00
parent 22dd836508
commit 65fd4cb65b
7 changed files with 19 additions and 9 deletions

View File

@ -498,7 +498,7 @@ Description: Information about CPU vulnerabilities
"Mitigation: $M" CPU is affected and mitigation $M is in effect "Mitigation: $M" CPU is affected and mitigation $M is in effect
Details about the l1tf file can be found in Details about the l1tf file can be found in
Documentation/admin-guide/l1tf.rst Documentation/admin-guide/hw-vuln/l1tf.rst
What: /sys/devices/system/cpu/smt What: /sys/devices/system/cpu/smt
/sys/devices/system/cpu/smt/active /sys/devices/system/cpu/smt/active

View File

@ -0,0 +1,12 @@
========================
Hardware vulnerabilities
========================
This section describes CPU vulnerabilities and provides an overview of the
possible mitigations along with guidance for selecting mitigations if they
are configurable at compile, boot or run time.
.. toctree::
:maxdepth: 1
l1tf

View File

@ -17,14 +17,12 @@ etc.
kernel-parameters kernel-parameters
devices devices
This section describes CPU vulnerabilities and provides an overview of the This section describes CPU vulnerabilities and their mitigations.
possible mitigations along with guidance for selecting mitigations if they
are configurable at compile, boot or run time.
.. toctree:: .. toctree::
:maxdepth: 1 :maxdepth: 1
l1tf hw-vuln/index
Here is a set of documents aimed at users who are trying to track down Here is a set of documents aimed at users who are trying to track down
problems and bugs in particular. problems and bugs in particular.

View File

@ -2114,7 +2114,7 @@
Default is 'flush'. Default is 'flush'.
For details see: Documentation/admin-guide/l1tf.rst For details see: Documentation/admin-guide/hw-vuln/l1tf.rst
l2cr= [PPC] l2cr= [PPC]

View File

@ -1107,7 +1107,7 @@ static void __init l1tf_select_mitigation(void)
pr_info("You may make it effective by booting the kernel with mem=%llu parameter.\n", pr_info("You may make it effective by booting the kernel with mem=%llu parameter.\n",
half_pa); half_pa);
pr_info("However, doing so will make a part of your RAM unusable.\n"); pr_info("However, doing so will make a part of your RAM unusable.\n");
pr_info("Reading https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html might help you decide.\n"); pr_info("Reading https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html might help you decide.\n");
return; return;
} }

View File

@ -6801,8 +6801,8 @@ static struct kvm_vcpu *vmx_create_vcpu(struct kvm *kvm, unsigned int id)
return ERR_PTR(err); return ERR_PTR(err);
} }
#define L1TF_MSG_SMT "L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details.\n" #define L1TF_MSG_SMT "L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.\n"
#define L1TF_MSG_L1D "L1TF CPU bug present and virtualization mitigation disabled, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/l1tf.html for details.\n" #define L1TF_MSG_L1D "L1TF CPU bug present and virtualization mitigation disabled, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.\n"
static int vmx_vm_init(struct kvm *kvm) static int vmx_vm_init(struct kvm *kvm)
{ {