From mboxrd@z Thu Jan 1 00:00:00 1970 References: <20170329203908.GA39222@beast> From: Dave Hansen Message-ID: Date: Wed, 29 Mar 2017 14:19:37 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: [kernel-hardening] Re: [PATCH] x86/fpu: move FPU state into separate cache To: Kees Cook , "H. Peter Anvin" Cc: LKML , Rik van Riel , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , "x86@kernel.org" , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Peter Zijlstra , 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 , "kernel-hardening@lists.openwall.com" List-ID: On 03/29/2017 02: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). This adjacency (or not) isn't really the > problem: it's that FPU state size is only known at runtime. Another > solution would be to have FPU state be a fixed size... We don't want that. It varies from a couple hundred bytes to ~3k on newer CPUs. We don't want to eat an extra 2.5k per task on the older processors.