[lkml]   [2017]   [Mar]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] x86/fpu: move FPU state into separate cache
On Wed, Mar 29, 2017 at 2:30 PM, Linus Torvalds
<> wrote:
> On Wed, Mar 29, 2017 at 2:09 PM, Kees Cook <> wrote:
>> They're adjacent already, which poses a problem for the struct layout
>> randomization plugin, since adjacency may no longer be true (after
>> layout randomization). T
> What?
> The layout randomization can't change anything, if you just make the
> adjacency be done explicitly instead of by having the thing be a fixed
> member.
> The trivial model might be to just declare the fpu part as an unsized
> array at the end:
> /* Floating point and extended processor state */
> struct fpu fpu[];
> because there is no way in hell that any randomization code can move
> those kinds of unsized arrays around. If it does, the gcc plugin is
> such unbelievable garbage that it would be insane to depend on such
> shit in the first place.

Randomization also needs to leave thread_info at the beginning. Can it do that?

 \ /
  Last update: 2017-03-29 23:39    [W:0.066 / U:0.608 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site