On Tue, 2014-08-19 at 12:13 -0500, Grant Likely wrote:
> On Tue, Aug 19, 2014 at 11:43 AM, David Woodhouse <dwmw2@infradead.org> wrote:
> > On Tue, 2014-08-19 at 08:47 -0700, Guenter Roeck wrote:
> >>
> >> If you want to taint the kernel on module removal because it is known that many
> >> drivers have bugs in their removal code,
> >
> > Most drivers don't have "removal code" per se. They have "unbind" code.
> > Which you can still exercise without actually unloading the driver.
> 
> Many platform, i2c, spi drivers have moved to macro generated module
> removal code that does nothing but unregister the struct
> device_driver.

That's exactly what I mean. There is no interesting code for unloading
the module. There is only the code for unbinding the device from the
driver (as in hot-unplug). Which doesn't go away if you disable module
unloading. It just gets harder to test.

-- 
dwmw2