On Fri, 6 Jan 2006, Pete Zaitcev wrote:

> On Sat, 7 Jan 2006 00:58:03 +0100, Oliver Neukum <[EMAIL PROTECTED]> wrote:
> 
> > The callback will not wake the tasks on the waitqueue if disconnect has
> > proceeded to mark the device as not present. This seems incorrect.
> > Comments?
> 
> It is incorrect, indeed. In real life this does not matter,
> because callbacks are served with -84 status before a disconnect
> has a chance to run (it has to have khubd awaken before that happens).
> But if you want to fix it, be my guest. The way to test this is
> to cause disconnect without a real disconnect, by doing rmmod,
> for example.

I agree that the code is incorrect and should be fixed.

You can't test it by doing rmmod, though, because the open file reference
will prevent rmmod from working.  Using sysfs to unbind the driver ought
to work.

Alan Stern



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to