Hi Greg, I found this issue when build testing your latest cleanup series with Sparse enabled. Clearly it was not caused by your series, it just helped me expose the problem since I built drivers I don't normally build. Anyway, a too large bInterval will end up zeroing urb->interval and in turn might confuse HCD's transfer scheduling routines. I wonder if these should be backported to stable tree, but so far nobody has complained, so perhaps not; your call cheers Felipe Balbi (3): usb: atm: speedtch: be careful with bInterval usb: class: cdc-acm: be careful with bInterval usb: clamp bInterval to allowed range drivers/usb/atm/speedtch.c | 2 +- drivers/usb/class/cdc-acm.c | 2 +- include/linux/usb.h | 4 ++++ 3 files changed, 6 insertions(+), 2 deletions(-) -- 1.8.2.1 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
