diff for duplicates of <1535651666.27823.6.camel@intel.com> diff --git a/a/content_digest b/N1/content_digest index c1f371f..8e4fafc 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -32,7 +32,9 @@ Nadav Amit <nadav.amit@gmail.com> Oleg Nesterov <oleg@redhat.com> Pavel Machek <pavel@ucw.cz> - " Peter Zijlstra <peterz@infradead>\0" + Peter Zijlstra <peterz@infradead.org> + ravi.v.shankar@intel.com + " vedvyas.shanbhogue@intel.com\0" "\00:1\0" "b\0" "On Thu, 2018-08-30 at 10:33 -0700, Dave Hansen wrote:\n" @@ -56,4 +58,4 @@ "\n" Yu-cheng -32c1c34acaabcffbec71a79834bb444ea0ee058e2c2003868abcc60c49d49628 +04b8ebe65e28cfda36aa5fea83da38c05606e26248234da1836e4608ab1186fa
diff --git a/a/1.txt b/N2/1.txt index 5ba4d5c..9ae3ad5 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -6,15 +6,15 @@ On Thu, 2018-08-30 at 10:33 -0700, Dave Hansen wrote: > > there, which cannot be used as a return address. > The overall concern is that we could overflow into a page that we > did -> not intend. Either another actual shadow stack or something that a +> not intend.A A Either another actual shadow stack or something that a > page > that the attacker constructed, like the transient scenario Jann > described. > A task could go beyond the bottom of its shadow stack by doing either -'ret' or 'incssp'. If it is the 'ret' case, the token prevents it. - If it is the 'incssp' case, a guard page cannot prevent it entirely, +'ret' or 'incssp'. A If it is the 'ret' case, the token prevents it. +A If it is the 'incssp' case, a guard page cannot prevent it entirely, right? Yu-cheng diff --git a/a/content_digest b/N2/content_digest index c1f371f..a12aeea 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -32,7 +32,9 @@ Nadav Amit <nadav.amit@gmail.com> Oleg Nesterov <oleg@redhat.com> Pavel Machek <pavel@ucw.cz> - " Peter Zijlstra <peterz@infradead>\0" + Peter Zijlstra <peterz@infradead.org> + ravi.v.shankar@intel.com + " vedvyas.shanbhogue@intel.com\0" "\00:1\0" "b\0" "On Thu, 2018-08-30 at 10:33 -0700, Dave Hansen wrote:\n" @@ -43,17 +45,17 @@ "> > there, which cannot be used as a return address.\n" "> The overall concern is that we could overflow into a page that we\n" "> did\n" - "> not intend.\302\240\302\240Either another actual shadow stack or something that a\n" + "> not intend.A A Either another actual shadow stack or something that a\n" "> page\n" "> that the attacker constructed, like the transient scenario Jann\n" "> described.\n" "> \n" "\n" "A task could go beyond the bottom of its shadow stack by doing either\n" - "'ret' or 'incssp'. \302\240If it is the 'ret' case, the token prevents it.\n" - "\302\240If it is the 'incssp' case, a guard page cannot prevent it entirely,\n" + "'ret' or 'incssp'. A If it is the 'ret' case, the token prevents it.\n" + "A If it is the 'incssp' case, a guard page cannot prevent it entirely,\n" "right?\n" "\n" Yu-cheng -32c1c34acaabcffbec71a79834bb444ea0ee058e2c2003868abcc60c49d49628 +b8e81a5493cade46aeb6e08e154a7ec93622afad0ef47533e22d9d8b57022b64
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.