From: Ben Greear <greearb@candelatech•com>
To: David Miller <davem@davemloft•net>
Cc: khc@pm•waw.pl, netdev@vger•kernel.org
Subject: Re: Why is gre0 auto-created, and can we fix it?
Date: Sun, 22 Jan 2012 08:48:53 -0800 [thread overview]
Message-ID: <4F1C3DF5.8070802@candelatech.com> (raw)
In-Reply-To: <20120121.134036.1565691107664746948.davem@davemloft.net>
On 01/21/2012 10:40 AM, David Miller wrote:
> From: Ben Greear<greearb@candelatech•com>
> Date: Sat, 21 Jan 2012 09:48:52 -0800
>
>> On 01/21/2012 09:39 AM, Krzysztof Halasa wrote:
>>> Ben Greear<greearb@candelatech•com> writes:
>>>
>>>>>> As far as I can tell, no other interfaces are auto-created
>>>>>> in this manner.
>>>>>
>>>>> ip6tnl0 and sit0 do it too, just grep for alloc_netdev() under
>>>>> net/{ipv4,ipv6}/
>>>>
>>>> So, no changing the behaviour?
>>>
>>> Perhaps making it CONFIGurable would be safe enough, not that I like
>>> CONFIG options for all tiny details (one may argue it's not a tiny
>>> detail).
>>>
>>> Haven't looked at the actual code.
>>
>> Seems like it could be a run-time configurable, maybe module or boot
>> option
>> or sysctl or something.
>
> I would seriously prefer that you not do this.
Just to make sure I understand you: You dislike any possible method of changing
the behaviour, not just the ones I listed?
If I do post a patch, it will be just for comment should someone
else want to carry the patch privately, and I'll just carry the patch
in my tree.
Thanks,
Ben
--
Ben Greear <greearb@candelatech•com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-01-22 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 19:49 Why is gre0 auto-created, and can we fix it? Ben Greear
2012-01-03 19:59 ` David Miller
2012-01-03 20:03 ` Ben Greear
2012-01-03 20:11 ` David Miller
2012-01-21 17:39 ` Krzysztof Halasa
2012-01-21 17:48 ` Ben Greear
2012-01-21 18:40 ` David Miller
2012-01-22 16:48 ` Ben Greear [this message]
2012-01-22 19:14 ` David Miller
2012-01-22 19:43 ` Stephen Hemminger
2012-01-22 21:00 ` Ben Greear
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=4F1C3DF5.8070802@candelatech.com \
--to=greearb@candelatech$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=khc@pm$(echo .)waw.pl \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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