Re: [linux-usb-devel] [RFC] consolidate /sbin/hotplug call for pci and

[David Brownell]

> I also found the unload USB module problem.  The driver core was calling
> hotplug after the device was already removed.  Made it a bit difficult
> to be able to describe the device that way :)

On the other hand, since there's no internal "this is an ex-device"
state, that's also insurance that nothing could use "usbfs" to try
to re-activate the device.  I seem to recall oopses going away by
reporting the hotplug "remove" events after the usbfs path could
no longer be used.  Not that I ever liked that consequence, but
a fix adding such a "zombie" state would have taken a bit of time.

The real "module unload problem" has a lot to do with not having any
way to track how many devices a module is bound to ... that aren't
necessarily opened at the moment.  (Does Rusty's patch set touch
any of that?)

Without having a way to answer that question, today's un-helpful
"driver is in active use" refcount would encourage rmmodding drivers
that users will expect to still be available.  Plug in two devices,
look at one, decide to use the other, unplug the first ... and just
because you hadn't yet opened the second device, its driver module
vanishes.  As you start to use it ... huge frustration quotient! :)

- Dave