From: Frederic Weisbecker <fweisbec@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: paulmck@linux.vnet.ibm.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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>
Subject: Re: [PATCH] make CONFIG_EXPERIMENTAL invisible and default
Date: Wed, 3 Oct 2012 23:31:28 +0200 [thread overview]
Message-ID: <20121003213117.GD637@somewhere> (raw)
In-Reply-To: <CAGXu5jJhEpdwCqYc0hWs504snMZg9FMygUjLwRUSyaKGAfXb5Q@mail.gmail.com>
On Wed, Oct 03, 2012 at 11:43:32AM -0700, Kees Cook wrote:
> I would expect a simple addition of "this is dangerous/buggy" to the
> description and "default n" is likely the way to go for that kind of
> thing.
Agreed.
> I think the history of CONFIG_EXPERIMENTAL has proven there
> isn't a sensible way to create a global flag for this kind of thing.
> To paraphrase Serge: my experimental options are not your experimental
> options.
> For example, some of the things that already had the experimental
> config removed, they left the "(EXPERIMENTAL)" in their config title.
Right.
next prev parent reply other threads:[~2012-10-03 21:31 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 [this message]
2012-10-08 22:08 ` Kees Cook
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=20121003213117.GD637@somewhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.