Hi, While reviewing all users of usb_anchor-s (because of some usb_anchor fixes I've been writing), I noticed that btusb normally puts to be transmitted urbs on an anchor called tx_anchor and then submits them, unless suspended, then they are put on an anchor called deferred without being submitted. On resume any urbs on the deferred anchor get removed from the deferred anchor, and submitted to the device. But unlike other drivers which similar constructs, btusb does not move put them on the tx_anchor when submitting then from the resume handler. So after a resume with deferred transmits, there will be tx urbs in flight which are not anchored on the tx_anchor. I believe this is a bug, but I don't know the code well enough to be sure. Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
