Peter Memishian wrote:
> I suppose that's one way to do it. What happens if I just do a
> modload() and simply keep the module from unloading (I can do that since
> I have control of the plugin specific reference count)? Is that
> considered in bad taste?
Can you say more about how this reference count prevents someone from
doing an explicit `modunload' of the module?
The modunload() will get to the plugin's _fini() routine, which will try
to to a mactype_unregister(). mactype_unregister() will return EBUSY
since the reference count kept by the mac module for that plugin will be
non-zero. The plugin's _fini() will then return EBUSY, thus failing the
modload().
-Seb
_______________________________________________
networking-discuss mailing list
[email protected]
