lkml.org 
[lkml]   [2019]   [Jan]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v3 5/6] x86/alternative: Use a single access in text_poke() where possible
On Thu, Jan 10, 2019 at 12:32:43PM -0500, Steven Rostedt wrote:
> On Thu, 10 Jan 2019 11:20:04 -0600
> Josh Poimboeuf <jpoimboe@redhat.com> wrote:
>
>
> > > While I can't find a reason for hypervisors to emulate this instruction,
> > > smarter people might find ways to turn it into a security exploit.
> >
> > Interesting point... but I wonder if it's a realistic concern. BTW,
> > text_poke_bp() also relies on undocumented behavior.
>
> But we did get an official OK from Intel that it will work. Took a bit
> of arm twisting to get them to do so, but they did. And it really is
> pretty robust.

Did we (they?) list any caveats for this behavior? E.g. I'm fairly
certain atomicity guarantees go out the window if WC memtype is used.

\
 
 \ /
  Last update: 2019-01-10 18:44    [W:0.125 / U:2.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site