Alan Stern wrote:
Sorry, my question wasn't clear. What I'm trying to understand is, after you had done
echo 0 >.../bConfigurationValue
why was any code calling usb_reset_device? And exactly which code was calling usb_reset_device?
USBDEVFS_RESET.
Seems to me that usb_physical_reset_device() should just be returning "early" when dev->actconfig is null It could re-read descriptors, but it shouldn't be trying to restore a non-existent configuration (or pick one).
Likely the simplest fix is just to fail at the very top of that routine if there's no configuration. That routine needs some significant changes, that'd be a way to avoid them and prevent user-initiated oopses.
Simple patch -- feel like making it? That one might even meet the 2.6.0 integration criteria.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
