[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1454684947.2779.12.camel@v3.sk>
Date: Fri, 05 Feb 2016 16:09:07 +0100
From: Lubomir Rintel <lkundrak@...sk>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH 2/3] dummy: make device count build-time configurable
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@...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@...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
Powered by blists - more mailing lists