Skip to contentSkip to conversation

Is an alternative module interface needed/possible?

RFC Adam J. Richter 2 participants 2 messages Feb 20, 2003

lore
Share & tools
lore
#0 lore raw

On 2003-02-20, Roman Zippel responded to Werner Almesberger:

Quoted 11 lines

The question is now whether we return an error value or use a callback. When a device is removed, we usually also want to remove all its data structures, on the other hand we can only remove a module when there are no users, so here we return an error value.
Now I need a bigger example to put this into a context, a nice example is scsi_unregister. It removes among other things procfs entries and these entries have a reference to struct Scsi_Host. As long as scsi_unregister is called from module_exit everything works fine, but a bit searching reveals drivers/usb/storage/usb.c, which create/removes a scsi host when you plug/unplug a storage device (let's ignore other problems here, like it's still mounted).

The ability to remove a module is generally independent of
whether or not there is any hardware present at that moment for which the module supplies a driver. Instead, the determining issue is whether there are file descriptors open for that driver.

Of course, if the necessary hardware was never present at any
time when the device driver's module was loaded, then there never will be any file descriptors open for the device driver.

Adam J. Richter     __     ______________   575 Oroville Road
[email protected]     \ /                  Milpitas, California 95035
+1 408 309-6081         | g g d r a s i l   United States of America

"Free Software For The Rest Of Us."

#1 lore raw

Hi,

Quoted 4 lines · Adam J. Richter

The ability to remove a module is generally independent of
whether or not there is any hardware present at that moment for which the module supplies a driver. Instead, the determining issue is whether there are file descriptors open for that driver.

I don't understand, what you're trying to say.
File descriptors are not the only way to access a driver and the ability to remove a module is only dependent on the number of references to this module.

bye, Roman