On Thu, Sep 24, 2015 at 03:51:37PM -0700, David Miller wrote: > From: Andrew Lunn <andrew@xxxxxxx> > Date: Fri, 25 Sep 2015 00:26:54 +0200 > > > On Thu, Sep 24, 2015 at 03:15:54PM -0700, David Miller wrote: > >> From: Andrew Lunn <andrew@xxxxxxx> > >> Date: Thu, 24 Sep 2015 23:57:31 +0200 > >> > >> > I built the FEC driver as a module, and it won't unload: > >> > > >> > kernel:unregister_netdevice: waiting for eth1 to become free. Usage count = 1 > >> > unregister_netdevice: waiting for eth1 to become free. Usage count = 1 > >> > > >> > i assume because DSA holds a reference. I've not tried a fully module > >> > build, DSA has issues with that. > >> > > >> > Tested-by: Andrew Lunn <andrew@xxxxxxx> > >> > >> So, is this a regression? > > > > Sorry, worded that badly. Since DSA is still active, it should not be > > possible to unload the FEC driver. DSA should have a reference to it, > > and mdio-mux also should have a reference to the mdio bus of the FEC > > driver. > > > > As Russell requested, i will re-test without his patches, just to make > > sure. > > Something needs to hold into the underlying device refcount of a DSA > blob so that an unload can't even be attempted in that state. Holding a reference on a struct device does _not_ stop the device being unbound or the module driving it being removed. It merely stops the struct device from being freed before all references have been dropped. Devices are always free to be unbound from their bound drivers irrespective of the struct device refcount. Even taking a reference on the module (via try_module_get()) does not stop this. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
