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:19:37 -0700
From: Dave Hansen <>
To: Kees Cook <>, "H. Peter Anvin" <>
Cc: LKML <>, Rik van Riel <>,
 Andy Lutomirski <>, Thomas Gleixner <>,
 Ingo Molnar <>, "" <>,
 Paolo Bonzini <>, Radim Krčmář
 <>, 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 <>,
 "" <>
Subject: Re: [PATCH] x86/fpu: move FPU state into separate cache

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

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.