David Brownell wrote:
> > Incidentally, my tty driver's close routine unlinks urbs, my disconnect
> > routine frees the urbs. Is it dangerous to unlink urb's after they're
> > freed?
>
> Only if you dislike oopses! :)
>
Oh, I do dislike those.
> Driver disconnect() routines need to unlink ALL urbs as well as
> make sure that no other driver entries (file operations, say) will
> ever try to use that device again (even while unlinking proceeds).
>
Then I hope that disconnect() is not called on an irq!
Now let me think for a second. I'm not an expert on the Linux scheduler, but
if I recall correctly it's possible for a process to be swapped out (in the
middle of a file operation, say) when the timer interrupt fires. I could be
wrong about that. But if not, then it seems that while it's out,
disconnect() might get called. When the process runs again, how will it know
not to use that device?
--gmcnutt
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
