On Wed, 2015-07-29 at 02:06 +0000, Hayes Wang wrote: > Oliver Neukum [mailto:oneukum@xxxxxxxx] > > Sent: Tuesday, July 28, 2015 8:59 PM > [...] > > > > > static void rtl8152_tx_timeout(struct net_device *netdev) { > > > > > struct r8152 *tp = netdev_priv(netdev); > > > > > - int i; > > > > > > > > > > netif_warn(tp, tx_err, netdev, "Tx timeout\n"); > > > > > - for (i = 0; i < RTL8152_MAX_TX; i++) > > > > > - usb_unlink_urb(tp->tx_info[i].urb); > > > > > + > > > > > + usb_queue_reset_device(tp->intf); > > > > > + cancel_delayed_work(&tp->schedule); > > > > > > > > Sorry to bother you again, but this looks wrong. > > > > You want to cancel first. There is no point in running any work > > > > before the reset is done. It will undo any progress anyway. > > > > > > Excuse me. Do you mean I don't need cancel the other work because it > > > wouldn't be run before the reset is finished? > > > > No, whatever the other work will do, the reset will undo. > > Excuse me. I don't understand why I couldn't use usb_queue_reset_device() directly. > Why the reset will undo? Now, I think I got the reason for the confusion. You are using cancel_delayed_work(&tp->schedule); after you queue a reset. Therefore the order in which the work and the reset will be executed is undefined. Usually the scheduled work will be canceled, but not always. That is not good. Regards Oliver -- 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
