GitHub-Mirror/Star64_linux
2
0
Fork 0
mirror of https://github.com/Fishwaldo/Star64_linux.git synced 2025-06-26 16:41:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

admin-guide/hw-vuln: Rephrase a section of core-scheduling.rst

Browse source 
Rephrase the "For MDS" section in core-scheduling.rst for the purpose of
making it clearer what is meant by "kernel memory is still considered
untrusted".

Suggested-by: Vineeth Pillai <Vineeth.Pillai@microsoft.com>
Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Reviewed-by: Joel Fernandes (Google) <joelaf@google.com>
Link: https://lore.kernel.org/r/20210721190250.26095-1-fmdefrancesco@gmail.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
Fabio M. De Francesco 2021-07-21 21:02:50 +02:00 • committed by Jonathan Corbet
parent b426d9d78e
commit ce48ee81a1
1 changed files with 6 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

10
Documentation/admin-guide/hw-vuln/core-scheduling.rst
View file

@ -181,10 +181,12 @@ Open cross-HT issues that core scheduling does not solve
-------------------------------------------------------- --------------------------------------------------------
1. For MDS 1. For MDS
~~~~~~~~~~ ~~~~~~~~~~
Core scheduling cannot protect against MDS attacks between an HT running in Core scheduling cannot protect against MDS attacks between the siblings
user mode and another running in kernel mode. Even though both HTs run tasks running in user mode and the others running in kernel mode. Even though all
which trust each other, kernel memory is still considered untrusted. Such siblings run tasks which trust each other, when the kernel is executing
attacks are possible for any combination of sibling CPU modes (host or guest mode). code on behalf of a task, it cannot trust the code running in the
sibling. Such attacks are possible for any combination of sibling CPU modes
(host or guest mode).
2. For L1TF 2. For L1TF
~~~~~~~~~~~ ~~~~~~~~~~~