On Fri, Aug 31, 2012 at 4:59 PM, Eric W. Biederman <ebied...@xmission.com> wrote:
> From a overal kernel maintenance and use perspective the unconditional > enablement is a pain. > > We long ago established the principle that compiling additional code > into the kernel should not change the semenatics of the kernel. > > So this code needs to come with a command line or sysctl on/off switch > not an unconditional enable. Your argument makes zero sense. If I decide to build new code, that new code can do something. It happens all the time. If you don't like Yama, don't build Yama. If you don't like the only thing that Yama does (it only implements one protection), disable that protection from sysctl. I don't get it. -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
