From: "David S. Miller" <davem@redhat.com>
To: jgarzik@pobox.com
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: dev->xmit_lock_owner?
Date: Tue, 18 Feb 2003 16:02:41 -0800 (PST) [thread overview]
Message-ID: <20030218.160241.10142341.davem@redhat.com> (raw)
In-Reply-To: <20030218183306.GA31478@gtf.org>
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.
prev parent reply other threads:[~2003-02-19 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 18:33 dev->xmit_lock_owner? Jeff Garzik
2003-02-19 0:02 ` David S. Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030218.160241.10142341.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).