From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-kernel] Proper distribution integration of kernel *-sources, patches and configuration.
Date: Mon, 01 Jul 2013 17:17:07 -0400 [thread overview]
Message-ID: <51D1F1D3.8030402@gentoo.org> (raw)
In-Reply-To: <20130701192324.GA30808@kroah.com>
On 07/01/2013 03:23 PM, Greg KH wrote:
> On Mon, Jul 01, 2013 at 08:45:16PM +0200, Tom Wijsman wrote:
>>>> Q: What about my stable server? I really don't want to run this
>>>> stuff!
>>>>
>>>> A: These options would depend on !CONFIG_VANILLA or
>>>> CONFIG_EXPERIMENTAL
>>> What is CONFIG_VANILLA? I don't see that in the upstream kernel tree
>>> at all.
>>>
>>> CONFIG_EXPERIMENTAL is now gone from upstream, so you are going to
>>> have a problem with this.
>> Earlier I mentioned "2) These feature should depend on a non-vanilla /
>> experimental option." which is an option we would introduce under the
>> Gentoo distribution menu section.
> Distro-specific config options, great :(
I'm not sure what you mean by "distro-specific", but suppose people want
BFQ? Why can't we have it in gentoo-sources. It is totally disabled by
not selecting CONFIG_BFQ. Selecting it is no different than emerging
pf-sources with the same other options ported over. By your logic, we
should not distribut pf-sources either. The truth of the matter is,
there are forks of the vanilla kernel out there. Are you suggesting we
distribute none of them?
NOTE: hardened-sources is its own world. There is not level of turning
on/off options that get you back to a vanilla kernel.
>
>>>> which would be disabled by default, therefore if you keep this
>>>> option the way it is on your stable server; it won't affect you.
>>> Not always true. Look at aufs as an example. It patches the core
>>> kernel code in ways that are _not_ accepted upstream yet. Now you all
>>> are running that modified code, even if you don't want aufs.
>> Earlier I mentioned "3) The patch should not affect the build by
>> default."; if it does, we have to adjust it to not do that, this is
>> something that can be easily scripted. It's just a matter of embedding
>> each + block in the diff with a config check and updating the counts.
> Look at aufs as a specific example of why you can't do that, otherwise,
> don't you think that the aufs developer(s) wouldn't have done so?
>
> The goal of "don't touch any other kernel code" is a very good one, but
> not always true for these huge out-of-tree kernel patches. Usually that
> is the main reason why these patches aren't merged upstream, because
> those changes are not acceptable.
>
> So be very careful here, you are messing with things that are rejected
> by upstream.
>
> greg k-h
>
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next prev parent reply other threads:[~2013-07-01 21:15 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 14:41 [gentoo-dev] Proper distribution integration of kernel *-sources, patches and configuration Tom Wijsman
2013-07-01 15:14 ` Ben de Groot
2013-07-01 15:20 ` [gentoo-dev] Re: [gentoo-kernel] " Jeff Horelick
2013-07-01 18:30 ` Anthony G. Basile
2013-07-01 19:07 ` Tom Wijsman
2013-07-01 19:24 ` Greg KH
2013-07-01 19:40 ` Tom Wijsman
2013-07-01 19:55 ` Fabio Erculiani
2013-07-01 19:59 ` Pacho Ramos
2013-07-01 20:03 ` Fabio Erculiani
2013-07-01 20:06 ` Tom Wijsman
2013-07-01 20:24 ` Christoph Junghans
2013-07-01 20:27 ` Fabio Erculiani
2013-07-01 20:25 ` Rick "Zero_Chaos" Farina
2013-07-01 21:18 ` Anthony G. Basile
2013-07-01 16:20 ` [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-07-01 16:28 ` hasufell
2013-07-01 17:35 ` Tom Wijsman
2013-07-01 17:52 ` Rick "Zero_Chaos" Farina
2013-07-05 0:19 ` Mike Pagano
2013-07-17 21:11 ` Donnie Berkholz
2013-07-01 18:17 ` [gentoo-dev] Re: [gentoo-kernel] " Greg KH
2013-07-01 18:38 ` Markos Chandras
2013-07-01 18:56 ` Tom Wijsman
2013-07-01 19:09 ` Matthew Summers
2013-07-01 19:25 ` Tom Wijsman
2013-07-01 19:33 ` Greg KH
2013-07-01 19:50 ` Tom Wijsman
2013-07-03 10:45 ` [gentoo-dev] " Steven J. Long
2013-07-03 12:42 ` Tom Wijsman
2013-07-04 2:00 ` Walter Dnes
2013-07-04 5:37 ` [gentoo-dev] " Steven J. Long
2013-07-04 7:41 ` [gentoo-dev] " Tom Wijsman
2013-07-04 5:27 ` [gentoo-dev] " Steven J. Long
2013-07-04 7:57 ` Tom Wijsman
2013-07-05 8:38 ` Steven J. Long
2013-07-05 9:04 ` Tom Wijsman
2013-07-09 15:12 ` Steven J. Long
2013-07-01 20:14 ` Markos Chandras
2013-07-01 20:25 ` Fabio Erculiani
2013-07-01 21:26 ` Anthony G. Basile
2013-07-01 21:30 ` Fabio Erculiani
2013-07-01 21:55 ` Anthony G. Basile
2013-07-01 20:31 ` Tom Wijsman
2013-07-01 18:45 ` Tom Wijsman
2013-07-01 19:23 ` Greg KH
2013-07-01 19:33 ` Tom Wijsman
2013-07-01 21:17 ` Anthony G. Basile [this message]
2013-07-01 21:24 ` Greg KH
2013-07-01 21:53 ` Anthony G. Basile
2013-07-02 8:31 ` gentoo-checkconf script " Michael Weber
2013-07-03 11:40 ` [gentoo-dev] Re: gentoo-checkconf script " Steven J. Long
2013-07-01 21:55 ` [gentoo-dev] " Tom Wijsman
2013-07-02 1:36 ` Richard Yao
2013-07-02 1:44 ` Richard Yao
2013-07-02 1:56 ` Greg KH
2013-07-02 3:29 ` Richard Yao
2013-07-02 3:40 ` Richard Yao
2013-07-02 19:39 ` Greg KH
2013-07-02 3:31 ` Richard Yao
2013-07-02 7:36 ` [gentoo-dev] " Sergei Trofimovich
2013-07-02 8:21 ` Fabio Erculiani
2013-07-02 8:37 ` Michael Weber
2013-07-02 8:52 ` Michael Weber
2013-07-02 18:16 ` Sergei Trofimovich
2013-07-03 13:06 ` Tom Wijsman
2013-07-03 13:52 ` Sergei Trofimovich
2013-07-03 15:18 ` Tom Wijsman
2013-07-03 16:10 ` Sergei Trofimovich
2013-07-02 10:08 ` Tom Wijsman
2013-07-02 21:48 ` Tomáš Pružina
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=51D1F1D3.8030402@gentoo.org \
--to=blueness@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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