>>> On 29.04.11 at 09:25, David Miller <davem@xxxxxxxxxxxxx> wrote: > From: "Jan Beulich" <JBeulich@xxxxxxxxxx> > 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 <jbeulich@xxxxxxxxxx> >> Cc: Jeff Mahoney <jeffm@xxxxxxxx> > > 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 _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
