dev->xmit_lock_owner?
Subsystems (2)
hum.
It seems that dev_watchdog, among other places, does not assign a value to dev->xmit_lock_owner, when it takes the lock.
I think this is a bug, but could be wrong ;-)
From: Jeff Garzik <[email protected]>
Date: Tue, 18 Feb 2003 13:33:06 -0500
It seems that dev_watchdog, among other places, does not assign a value to dev->xmit_lock_owner, when it takes the lock.
I think this is a bug, but could be wrong ;-)
Not a bug, only pieces of the transmit path need to follow this rule. It's only meant to detect devices which have been chained in a way which forms a loop during transmit.