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
| ||
|
Message-Id: <20201028121917.635203-2-jbwyatt4@gmail.com> Date: Wed, 28 Oct 2020 05:19:10 -0700 From: "John B. Wyatt IV" <jbwyatt4@...il.com> To: "' Joel Fernandes (Google)" <joel@...lfernandes.org>, Nishanth Aravamudan <naravamudan@...italocean.com>, Julien Desfossez <jdesfossez@...italocean.com>, Peter Zijlstra <peterz@...radead.org>, Tim Chen <tim.c.chen@...ux.intel.com>, Vineeth Pillai <viremana@...ux.microsoft.com>, Aaron Lu <aaron.lwe@...il.com>, Aubrey Li <aubrey.intel@...il.com>, tglx@...utronix.de, linux-kernel@...r.kernel.org, mingo@...nel.org, torvalds@...ux-foundation.org, fweisbec@...il.com, keescook@...omium.org, kerrnel@...gle.com, Phil Auld <pauld@...hat.com>, Valentin Schneider <valentin.schneider@....com>, Mel Gorman <mgorman@...hsingularity.net>, Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, Paolo Bonzini <pbonzini@...hat.com>, vineeth@...byteword.org, Chen Yu <yu.c.chen@...el.com>, Christian Brauner <christian.brauner@...ntu.com>, Agata Gruza <agata.gruza@...el.com>, Antonio Gomez Iglesias <antonio.gomez.iglesias@...el.com>, graf@...zon.com, konrad.wilk@...cle.com, dfaggioli@...e.com, pjt@...gle.com, rostedt@...dmis.org, derkling@...gle.com, benbjiang@...cent.com, Alexandre Chartre <alexandre.chartre@...cle.com>, James.Bottomley@...senpartnership.com, OWeisse@...ch.edu, Dhaval Giani <dhaval.giani@...cle.com>, Junaid Shahid <junaids@...gle.com>, jsbarnes@...gle.com, chris.hyser@...cle.com, Aubrey Li <aubrey.li@...ux.intel.com>, "Paul E. McKenney" <paulmck@...nel.org>, Tim Chen ' <tim.c.chen@...el.com> Cc: "John B. Wyatt IV" <jbwyatt4@...il.com> Subject: [PATCH 1/8] sched: Correct misspellings in core-scheduling.rst 'priorty', 'guarenteed', 'guarentee' should be: priority, guaranteed, guarantee. Issue reported by checkpatch. Signed-off-by: John B. Wyatt IV <jbwyatt4@...il.com> --- Documentation/admin-guide/hw-vuln/core-scheduling.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Documentation/admin-guide/hw-vuln/core-scheduling.rst b/Documentation/admin-guide/hw-vuln/core-scheduling.rst index eacafbb8fa3f..638d0f3c1c09 100644 --- a/Documentation/admin-guide/hw-vuln/core-scheduling.rst +++ b/Documentation/admin-guide/hw-vuln/core-scheduling.rst @@ -161,7 +161,7 @@ priority task is not trusted with respect to the core wide highest priority task. If a sibling does not have a trusted task to run, it will be forced idle by the scheduler(idle thread is scheduled to run). -When the highest priorty task is selected to run, a reschedule-IPI is sent to +When the highest priority task is selected to run, a reschedule-IPI is sent to the sibling to force it into idle. This results in 4 cases which need to be considered depending on whether a VM or a regular usermode process was running on either HT:: @@ -223,9 +223,9 @@ Also this does nothing about syscall entries. 3. Kernel Address Space Isolation ################################# System calls could run in a much restricted address space which is -guarenteed not to leak any sensitive data. There are practical limitation in +guaranteed not to leak any sensitive data. There are practical limitation in implementing this - the main concern being how to decide on an address space -that is guarenteed to not have any sensitive data. +that is guaranteed to not have any sensitive data. 4. Limited cookie-based protection ################################## @@ -251,7 +251,7 @@ outside. Tasks outside the group also don't trust tasks within. Limitations ----------- -Core scheduling tries to guarentee that only trusted tasks run concurrently on a +Core scheduling tries to guarantee that only trusted tasks run concurrently on a core. But there could be small window of time during which untrusted tasks run concurrently or kernel could be running concurrently with a task not trusted by kernel. -- 2.28.0
Powered by blists - more mailing lists