Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 29 Mar 2017 14:30:02 -0700
From: Linus Torvalds <>
To: Kees Cook <>
Cc: "H. Peter Anvin" <>, LKML <>, 
	Rik van Riel <>, Andy Lutomirski <>, Thomas Gleixner <>, 
	Ingo Molnar <>, "" <>, Paolo Bonzini <>, 
	Radim Krčmář <>, 
	Peter Zijlstra <>, Dave Hansen <>, 
	Yu-cheng Yu <>, Masahiro Yamada <>, 
	Borislav Petkov <>, Christian Borntraeger <>, 
	Thomas Garnier <>, Brian Gerst <>, 
	He Chen <>, Mathias Krause <>, 
	Fenghua Yu <>, Piotr Luc <>, Kyle Huey <>, 
	Len Brown <>, KVM <>, 
	"" <>
Subject: Re: [PATCH] x86/fpu: move FPU state into separate cache

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


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

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.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.