As in, "no effect" or "the big issue didn't go away"?Yeah, that suggests that either usb-storage needs to handle this somehow, right?Like by recognizing this case and reporting USB_STOR_XFER_SHORT? Likely that's so. It doesn't ... that "catch short read" logic (after that "catch-all") won't kick in.Hm, this patch doesn't solve anything :(
If "no effect", then I wonder why storage is distinguishing that
case at all. But it seems like it ought to handle the -EREMOTEIO
short read cass like the other one.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
