dev->xmit_lock_owner?

2 messages, 2 authors, 2003-02-19 · open the first message on its own page

dev->xmit_lock_owner?

From: Jeff Garzik <hidden>
Date: 2003-02-18 18:33:06

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 ;-)

Re: dev->xmit_lock_owner?

From: David S. Miller <hidden>
Date: 2003-02-19 00:02:41

   From: Jeff Garzik [off-list ref]
   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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help