On 01/05/2012 03:55 PM, Kees Cook wrote:
On Thu, Jan 5, 2012 at 12:08 PM, Nick Bowler<nbowler@xxxxxxxxxxxxxxxx> wrote:
But this is a brand new feature that changes longstanding behaviour of
various syscalls. Making it default to enabled is rather mean to users
(since it will tend to get enabled by "oldconfig") and seems almost
guaranteed to cause regressions.
I couldn't disagree more. There has been zero evidence of this change
causing anything but regressions in _attacks_. :P If anything, I think
there should be no CONFIG and no sysctl, and it should be entirely
non-optional. But since this patch needs consensus, I have provided
knobs to control it.
I agree with you, Kees.
The behaviour introduced by this patch should produce so
few issues, that the new behaviour should probably be on
by default.
The few people impacted can use a sysctl knob to disable
the check on their systems. I am not sure anyone will
actually be using that knob...
The config option is probably not needed. The new
behaviour is something that could just be on by default
for everyone, and disabled by the few (if any) people
who have some setup that breaks with it.
--
All rights reversed
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
