-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am Freitag, 7. Februar 2003 21:54 schrieb Duncan Sands:
> On Friday 07 February 2003 17:28, Oliver Neukum wrote:
> > > That was a guess - and it seems wrong (I should have taken the 30
> > > seconds needed to check...). I can't in fact see anything that stops
> > > the module being unloaded after a successful probe! I assumed that the
> > > driver would
> >
> > That's right. A driver can be unloaded even if it is bound to a device.
> > It's ununloadable only during probe/disconnect/ioctl through usbfs
> > itself. For anything more you are responsible yourself. That is usually
> > done useing the services the character device layer provides.
>
> Hi Oliver, I understand better now - both the new module subsystem and
> how USB uses it. However, the USB subsystem should be doing
> try_module_get before any call into a driver. But there is one case in
> which it doesn't: calling urb completion handlers. Isn't this wrong?
No. The driver's disconnect method is responsible for unlinking all URBs and
_wait_ for all completion handlers to finish. To do so a synchronous unlink
is the method of choice.
Thus a call to a completion handler is always harmless.
Regards
Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD8DBQE+RCA1Gd1iW7kgYIQRAjWqAJ4zSIcmHlcZTLCQk2kLdm87i37HYACfSiSB
HnrjnpUl1p+LjaIgrBQqPAc=
=7TRW
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
