Hi!
> > While I understand, there are a few users who will have problems with
> > this default are we really better to not provide this defense in depth
> > for the majority of users and let those with problems turn it off rather
> > than provide no defense by default? I could even provide a different
> > default for SELinux and non-SELinux if anyone saw value in that? But if
> > others think that off default is best I'll send another patch shortly
> > with the unsigned long fix and the default set to 0. My hope is then
> > that distros will figure out to turn this on.
> >
>
> I hope not. This breaks any hardware virtualizer.
>
> So yes, we're better off not having this on, and require it to be
> explicitly enabled by the end user.
You could do something like 4G+4G patches.... but performance penalty
would be ugly.
But no, we cant break userspace 'by default'.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
