[lkml]   [2011]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH v2 08/10] x86-64: Emulate vsyscalls

    * Andrew Lutomirski <> wrote:

    > On Mon, May 30, 2011 at 3:46 AM, Ingo Molnar <> wrote:
    > >
    > > * Andy Lutomirski <luto@MIT.EDU> wrote:
    > >
    > >> There's a fair amount of code in the vsyscall page, and who knows
    > >> what will happen if an exploit jumps into the middle of it.  Reduce
    > >> the risk by replacing most of it with short magic incantations that
    > >> are useless if entered in the middle.  This change can be disabled
    > >> by CONFIG_UNSAFE_VSYSCALLS (default y).
    > >
    > > btw., please flip the default or consider removing the option
    > > altogether.
    > >
    > > We want to improve security and we want safe vsyscalls the default,
    > > and it's no good if we make it too easy for users to keep the fire
    > > door open all the time! :-)
    > I'd advocate waiting until glibc 2.14 comes out with this change:
    > I want to add a warning (ratelimited to an extremely low rate) in v3
    > whenever any of the vsyscalls get used telling users that their legacy
    > code is suffering a performance impact, but it seems like bad form to
    > tell people to build glibc from git to avoid a regression.

    But only statically built binaries would be impacted in practice,
    right? The number of statically built binaries that heavily rely on
    vsyscalls ought to be a very small set ...


    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: 2011-05-30 13:03    [W:0.023 / U:31.048 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site