> What is a feature change like this doing coming in after the
quoted text
> merge window?

I considered it a "anti bloat bugfix". Adding 30k of 
object code to allno was a bit too much. 

quoted text
> Why doesn't an allnoconfig disable sysctl all together?

Because it depends on EMBEDDED and EMBEDDED is not y. Yes it's not
intuitive, on the other hand the end result is reasonable.

quoted text
> These are the only checks we have against someone doing something
> nasty in the sysctl hierarchy.   We have proven that we don't
> have the discipline to do the right thing with code in the
> core kernel.  I expect out of tree code will be much worse.

My assumption is that they will be run at least once during
a release cycle by someone and then the messages will appear
and be reported. We do the same thing with a lot of other
debug options (lockdep, slab debug, sleep debug etc.,). There's no 
need for this one to be special.

Also I'm not sure the check is all that useful anyways. We
should just not accept any new binary numbered sysctl, and
that's nearly the case anyways.

-Andi

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/