From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH] bridge: Module use count must be updated as bridges are created/destroyed Date: Fri, 29 Apr 2011 08:41:10 +0100 Message-ID: <4DBA87B6020000780003ED74@vpn.id2.novell.com> References: <4DBA830A020000780003ED5D@vpn.id2.novell.com> <20110429.002530.112581952.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8BIT Cc: , , , To: "David Miller" Return-path: In-Reply-To: <20110429.002530.112581952.davem@davemloft.net> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-ID: >>> On 29.04.11 at 09:25, David Miller wrote: > From: "Jan Beulich" > Date: Fri, 29 Apr 2011 08:21:14 +0100 > >> Otherwise 'modprobe -r' on a module having a dependency on bridge will >> implicitly unload bridge, bringing down all connectivity that was using >> bridges. >> >> Signed-off-by: Jan Beulich >> Cc: Jeff Mahoney > > All network device drivers behave exactly the same way, when you rmmod > the thing we unconfigure all the routes, addresses, etc. going through > that device and let you unload it. > > And this behavior is very much intentional. > > Don't add an exception here. You talk of rmmod on the very module, but the issue is about modprobe -r on a dependent module. I cannot believe you consider it correct that *implicit* unloading of bridge.ko should happen when bridges are configured. If the solution proposed isn't satisfactory, can you suggest a better alternative still serving the purpose? Jan