Maybe
> Could this result in certain race scenarios where a busy device´s
> hard_start_xmit() is called during a tx_timeout condition, the device
The theory is that dev->tbusy may get incorrectly cleared, but should never
be left incorrectly set. The reasoning here is that on the drivers transmit
code sets it.
If you can break that assumption you may be onto something. it doesnt seem
to explain why a module reload not an ifdown/ifup would be needed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/