netdev - Re: [PATCH 2/3] dummy: make device count build-time configurable

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160112104247.1004c32c@xeon-e3>
Date:	Tue, 12 Jan 2016 10:42:47 -0800
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	Lubomir Rintel <lkundrak@...sk>
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

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.