netdev - Re: [PATCH 3/3] bonding: 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: <20160112.154550.2297969991865269932.davem@davemloft.net>
Date:	Tue, 12 Jan 2016 15:45:50 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jay.vosburgh@...onical.com
Cc:	lkundrak@...sk, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, vfalico@...il.com,
	gospo@...ulusnetworks.com
Subject: Re: [PATCH 3/3] bonding: make device count build-time configurable

From: Jay Vosburgh <jay.vosburgh@...onical.com>
Date: Tue, 12 Jan 2016 08:34:12 -0800

> 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 bonding
>>  # ip link add bond0 type bond
>>  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.
> 
> 	I agree this is annoying, but I would expect distros to leave
> this set to 1 (for backwards compatibility with scripts that "modprobe
> bonding" then assume bond0 exists).  This leaves the problem in place
> for the vast majority of users.
> 
> 	Is there a reasonable way to resolve this that would actually
> fix things for regular distro kernel users?

Yeah I personally don't like this at all.

This behavior has 2 decades of precedence, it's therefore hard coded
into deep dark nooks and cranies of people's scripts.

Just be content with how things are, and document it better if need
be.