On Wed, Jul 21, 2021 at 11:44:23AM +0200, dave penkler wrote: > Sorry, the issue this patch is trying to fix occurs because the > current usbtmc driver resubmits the URB when it gets an EPROTO return. > The dummy usb host controller driver used in the syzbot tests keeps > returning the resubmitted URB with EPROTO causing a loop that starves > RCU. With an actual HCI driver it either recovers or returns an EPIPE. Are you sure about that? Have you ever observed a usbtmc device recovering and continuing to operate after an EPROTO error? An EPIPE error also seems rather unlikely -- particularly if the device is not plugged into a high-speed hub. Alan Stern > In either case no loop occurs. So for my part as a user and maintainer > this patch is not ok.
