From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Serge Hallyn <serge.hallyn@canonical.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] make CONFIG_EXPERIMENTAL invisible and default
Date: Mon, 8 Oct 2012 15:08:40 -0700 [thread overview]
Message-ID: <CAGXu5jL6N2qSokXFr17Re9DOneWx-+seSx7k_dk-A+0mgbOejQ@mail.gmail.com> (raw)
In-Reply-To: <20121003161702.GA22008@kroah.com>
On Wed, Oct 3, 2012 at 9:17 AM, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> On Wed, Oct 03, 2012 at 06:25:38AM -0700, Paul E. McKenney 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@linuxfoundation.org>
>> > CC: "Eric W. Biederman" <ebiederm@xmission.com>
>> > CC: Serge Hallyn <serge.hallyn@canonical.com>
>> > CC: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
>> > CC: Andrew Morton <akpm@linux-foundation.org>
>> > CC: Frederic Weisbecker <fweisbec@gmail.com>
>> > Signed-off-by: Kees Cook <keescook@chromium.org>
>> > ---
>> >
>> > 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?
>
> In the text say "You really don't want to enable this option, use at
> your own risk!" Or something like that :)
So, should I update the commit description to include a suggested
alternative? (If so, which one?)
Who is going to carry this initial patch, btw?
-Kees
--
Kees Cook
Chrome OS Security
next prev parent reply other threads:[~2012-10-08 22:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 19:50 [PATCH] make CONFIG_EXPERIMENTAL invisible and default Kees Cook
2012-10-02 21:40 ` Serge E. Hallyn
2012-10-03 13:25 ` Paul E. McKenney
2012-10-03 16:15 ` Kees Cook
2012-10-03 16:43 ` Josh Boyer
2012-10-03 16:16 ` Serge Hallyn
2012-10-03 16:17 ` Greg Kroah-Hartman
2012-10-03 16:47 ` Paul E. McKenney
2012-10-03 17:21 ` Greg Kroah-Hartman
2012-10-03 17:46 ` Frederic Weisbecker
2012-10-03 18:23 ` Josh Boyer
2012-10-03 19:36 ` Dave Jones
2012-10-03 20:05 ` Paul E. McKenney
2012-10-03 21:43 ` Frederic Weisbecker
2012-10-04 14:31 ` Paul E. McKenney
2012-10-03 17:46 ` Paul E. McKenney
2012-10-03 18:02 ` Serge Hallyn
2012-10-03 18:43 ` Kees Cook
2012-10-03 19:07 ` david
2012-10-03 20:03 ` Paul E. McKenney
2012-10-03 22:23 ` Eric W. Biederman
2012-10-04 0:11 ` Paul E. McKenney
2012-10-04 1:55 ` Matthew Garrett
2012-10-04 14:31 ` Paul E. McKenney
2012-10-05 16:46 ` Paul E. McKenney
2012-10-06 16:10 ` Frederic Weisbecker
2012-10-07 1:44 ` Paul E. McKenney
2012-10-07 2:33 ` Dave Airlie
2012-10-07 16:30 ` Paul E. McKenney
2012-10-07 20:18 ` Dave Jones
2012-10-08 1:04 ` Paul E. McKenney
2012-10-08 22:07 ` Kees Cook
2012-10-08 22:29 ` Paul E. McKenney
2012-10-08 22:37 ` Kees Cook
2012-10-08 22:40 ` Kees Cook
2012-10-08 22:59 ` Paul E. McKenney
2012-10-08 23:23 ` Kees Cook
2012-10-03 21:31 ` Frederic Weisbecker
2012-10-08 22:08 ` Kees Cook [this message]
2012-10-08 23:53 ` Greg Kroah-Hartman
2012-10-09 0:46 ` Kees Cook
2012-10-09 1:20 ` Greg Kroah-Hartman
2012-10-09 1:26 ` Paul E. McKenney
2012-10-09 1:57 ` Kees Cook
2012-10-09 2:47 ` Stephen Rothwell
2012-10-09 6:01 ` Kees Cook
2012-12-16 4:29 ` Jan Engelhardt
2012-12-16 16:19 ` Paul E. McKenney
2012-10-03 23:29 ` Guenter Roeck
2012-10-03 23:33 ` Kees Cook
2012-10-03 23:37 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGXu5jL6N2qSokXFr17Re9DOneWx-+seSx7k_dk-A+0mgbOejQ@mail.gmail.com \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=fweisbec@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=serge.hallyn@canonical.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).