From: Stephen Hemminger <shemminger@vyatta.com>
To: David Ward <david.ward@ll.mit.edu>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] dummy: do not create a link (dummy0) at module init by default
Date: Mon, 17 Jan 2011 08:56:42 -0800 [thread overview]
Message-ID: <20110117085642.0dddd66e@nehalam> (raw)
In-Reply-To: <1295225393-5779-1-git-send-email-david.ward@ll.mit.edu>
On Sun, 16 Jan 2011 19:49:53 -0500
David Ward <david.ward@ll.mit.edu> wrote:
> When the dummy network driver is initialized with no parameters, a link
> is automatically created (named 'dummy0'). This is inconsistent with
> other virtual network drivers such as veth, macvlan, and macvtap, which
> do not create a link upon initialization.
>
> This also causes confusing behavior when sending an RTM_NEWLINK message
> for a dummy link, because the kernel will load the dummy network driver
> first if it has not already been loaded. When that occurs, the result
> is that two new links are actually created (or if IFLA_IFNAME is set to
> 'dummy0', the error EEXIST is returned). The following iproute command
> demonstrates this behavior:
>
> ip link add [ name dummy0 ] type dummy
>
> With this change, users who still want to have a link created when the
> dummy network driver is loaded (instead of using iproute to create the
> link as shown above) just need to set the 'numdummies' parameter to 1:
>
> modprobe dummy numdummies=1
>
> Signed-off-by: David Ward <david.ward@ll.mit.edu>
I understand what you are trying to do, and it makes sense.
But because of the history behind this it can't change.
We can't change existing API and break user scripts.
The 'ip link' command support is new (in last couple of years), and
the module parameter has been around since early days.
If you want to load module without any devices just use:
modprobe dummy numdummies=0
--
prev parent reply other threads:[~2011-01-17 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 0:49 [PATCH] dummy: do not create a link (dummy0) at module init by default David Ward
2011-01-17 9:25 ` Jarek Poplawski
2011-01-17 16:56 ` Stephen Hemminger [this message]
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=20110117085642.0dddd66e@nehalam \
--to=shemminger@vyatta.com \
--cc=david.ward@ll.mit.edu \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).