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 15:28:58 -0700
To: Linus Torvalds <>,
        Andy Lutomirski <>
CC: Kees Cook <>, 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 March 29, 2017 2:41:00 PM PDT, Linus Torvalds <> wrote:
>On Wed, Mar 29, 2017 at 2:35 PM, Andy Lutomirski <>
>> Randomization also needs to leave thread_info at the beginning.  Can
>it do that?
>Good point, and good question. No idea if the gcc extension can do,
>but yes, it clearly needs a "you can't move this entry".
>I assume it has some such capability already, because it's fairly
>common to have that kind of "beginning of structure if fixed" due to
>unions of structures anyway.
>                 Linus

An alternative is to wrap the randomized structure inside a nonrandomized wrapper structure.
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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.