[lkml]   [2002]   [Apr]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: SSE related security hole
    On Fri, Apr 19, 2002 at 11:42:06PM +0200, Andi Kleen wrote:
    > On Fri, Apr 19, 2002 at 02:35:57PM -0700, H. Peter Anvin wrote:
    > > would initialize the entire FPU, including any state that future
    > > processors may add, thus reducing the likelihood of any funnies in the
    > > future.
    > That's also why I like it.

    Trusting the "boot state" of the cpu would require the BIOS to match the
    linux ABI. The FPU must be in a known initialized state at the linux
    level, not at the BIOS level, as first for the mxcsr, but also the other
    registers should be set to zero by default so gcc can exploit that (I
    guess that's what gcc is just doing and that's why Honza noticed it). so
    if new future processors will add new stuff, the new stuff will have to
    be initialized again in the "fxrestor" default payload in linux (so
    requiring a modification to the OS), and having to change the default
    rxrestor payload for a new cpu is equivalent to add another xor there
    (modulo the runtime check on the cpu features that could be avoided with
    two separate exception handlers for each cpu revision but it's fast
    enough that it doesn't matter at the moment on x86).

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:25    [W:0.023 / U:10.104 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site