I do not see a good solution at this time.
rwsem is a non-starter. IMHO, rwsems are optimizations for normal semaphores, and the code must remain correct regardless what is used.
Why is an additional lock needed at all? Why can't we just use devsem?
Also, what exactly is the correctness issue here?
It may be most effective to import 2.6 code for Speedtouch which has an in-kernel data processing loop. Since it does not do ioctls, it's immune to the exclusion. It's unfair to burden Speedtouch with TEAC problem though.
Yes. I have heard that atl least also eciadsl is similarly broken.
-- Meelis Roos ([EMAIL PROTECTED])
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
