Re: [PATCH] make CONFIG_EXPERIMENTAL invisible and default

[Josh Boyer]

On Wed, Oct 3, 2012 at 12:15 PM, Kees Cook <keescook@xxxxxxxxxxxx> wrote:
> On Wed, Oct 3, 2012 at 6:25 AM, Paul E. McKenney
> <paulmck@xxxxxxxxxxxxxxxxxx> wrote:
>> On Tue, Oct 02, 2012 at 12:50:42PM -0700, Kees Cook wrote:
>>> This config item has not carried much meaning for a while now and is
>>> almost always enabled by default. As agreed during the Linux kernel
>>> summit, it should be removed. As a first step, remove it from being
>>> listed, and default it to on. Once it has been removed from all
>>> subsystem Kconfigs, it will be dropped entirely.
>>>
>>> CC: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
>>> CC: "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>
>>> CC: Serge Hallyn <serge.hallyn@xxxxxxxxxxxxx>
>>> CC: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
>>> CC: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
>>> CC: Frederic Weisbecker <fweisbec@xxxxxxxxx>
>>> Signed-off-by: Kees Cook <keescook@xxxxxxxxxxxx>
>>> ---
>>>
>>> This is the first of a series of 202 patches removing EXPERIMENTAL from
>>> all the Kconfigs in the tree. Should I send them all to lkml (with all
>>> the associated CCs), or do people want to cherry-pick changes from my
>>> tree? I don't want to needlessly flood the list.
>>>
>>> http://git.kernel.org/?p=linux/kernel/git/kees/linux.git;a=shortlog;h=refs/heads/experimental
>>>
>>> I figure this patch can stand alone to at least make EXPERIMENTAL go
>>> away from the menus, and give us a taste of what the removal would do
>>> to builds.
>>
>> OK, I will bite...  How should I flag an option that is initially only
>> intended for those willing to take some level of risk?
>
> I'm not sure I understand what you mean? The intention of removing
> EXPERIMENTAL is effectively like turning it on everywhere, so this
> first patch does that. As we go forward we can remove the its
> redundant use in all the Kconfigs, until it is finally removed for
> real.

He's asking "how do I add a feature/option into Linus' tree that I'm
really not ready for random people and/or distros to enable".  The
short answer is "don't merge that into Linus' tree" I guess.  Keep it
in a git branch or patchset somewhere else.  Perhaps those willing to
take the risk are also willing to apply the patches?

josh
--
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/