Re: [3.1 patch] x86: default to vsyscall=native
From: Thomas Gleixner
Date: Wed Oct 05 2011 - 18:02:00 EST
On Thu, 6 Oct 2011, Adrian Bunk wrote:
> After upgrading a kernel the existing userspace should just work
> (assuming it did work before ;-) ), but when I upgraded my kernel
> from 3.0.4 to 3.1.0-rc8 a UML instance didn't come up properly.
> dmesg said:
> linux-18.104.22.168 vsyscall fault (exploit attempt?) ip:ffffffffff600000 cs:33 sp:7fbfb9c498 ax:ffffffffff600000 si:0 di:606790
> linux-22.214.171.124 vsyscall fault (exploit attempt?) ip:ffffffffff600000 cs:33 sp:7fbfb13168 ax:ffffffffff600000 si:0 di:606790
> Looking throught the changelog I ended up at commit 3ae36655
> ("x86-64: Rework vsyscall emulation and add vsyscall= parameter").
> Linus suggested in https://lkml.org/lkml/2011/8/9/376 to default to
> That sounds reasonable to me, and fixes the problem for me.
We have way too long listened to people who insisted that we keep all
known security holes open by default for the sake of backwards
Default wants to be restricted and not the other way round. Forcing
people to loosen restrictions makes them aware of the problem. Not
doing so keeps them in the illusion that stuff is just safe to use.
We might need better dmesg output, e.g.
printk_once("you might run something which requires
vsyscall=native, but be aware that you are
opening a security hole. See Documentation/....")
That's fine, but making the defaults insecure is just ass backwards.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/