* dev->xmit_lock_owner?
@ 2003-02-18 18:33 Jeff Garzik
2003-02-19 0:02 ` dev->xmit_lock_owner? David S. Miller
0 siblings, 1 reply; 2+ messages in thread
From: Jeff Garzik @ 2003-02-18 18:33 UTC (permalink / raw)
To: linux-net, netdev
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 ;-)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: dev->xmit_lock_owner?
2003-02-18 18:33 dev->xmit_lock_owner? Jeff Garzik
@ 2003-02-19 0:02 ` David S. Miller
0 siblings, 0 replies; 2+ messages in thread
From: David S. Miller @ 2003-02-19 0:02 UTC (permalink / raw)
To: jgarzik; +Cc: linux-net, netdev
From: Jeff Garzik <jgarzik@pobox.com>
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-02-19 0:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-02-18 18:33 dev->xmit_lock_owner? Jeff Garzik
2003-02-19 0:02 ` dev->xmit_lock_owner? David S. Miller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).