From: Lubomir Rintel <lkundrak@v3.sk>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/3] dummy: make device count build-time configurable
Date: Fri, 05 Feb 2016 16:09:07 +0100 [thread overview]
Message-ID: <1454684947.2779.12.camel@v3.sk> (raw)
In-Reply-To: <20160112104247.1004c32c@xeon-e3>
Hi Stephen,
On Tue, 2016-01-12 at 10:42 -0800, Stephen Hemminger wrote:
> On Tue, 12 Jan 2016 12:57:33 +0100
> Lubomir Rintel <lkundrak@v3.sk> wrote:
>
> > The devices can be created at run-time for quite some time already
> > and the
> > load-time device creation collides with attempts to create the
> > device of
> > the same name:
> >
> > # rmmod dummy
> > # ip link add dummy0 type dummy
> > RTNETLINK answers: File exists
> >
> > This is pretty much the same situation as was with the block loop
> > devices
> > which was solved by adding a build-time configuration that the
> > distributions could use as they deem fit while keeping the default
> > for
> > compatibility.
> >
> > Let's do that here as well.
> >
> > Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
>
> There is already a module parameter for this, so making it a compile
> time option adds nothing.
This option changes the defaults for the parameter.
When the module gets autoloaded, the user doesn't get a chance to
specify the module parameter and unwanted devices pop in.
Worse even, the automatically created devices are likely to collide
with what the user asked for.
Lubo
prev parent reply other threads:[~2016-02-05 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 11:57 [PATCH 2/3] dummy: make device count build-time configurable Lubomir Rintel
2016-01-12 18:42 ` Stephen Hemminger
2016-02-05 15:09 ` Lubomir Rintel [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=1454684947.2779.12.camel@v3.sk \
--to=lkundrak@v3.sk \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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