From: "David S. Miller" <davem@redhat.com>
To: eric@lammerts.org
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com, alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] wrong ENETDOWN in af_packet?
Date: Thu, 06 Mar 2003 10:31:42 -0800 (PST) [thread overview]
Message-ID: <20030306.103142.58817243.davem@redhat.com> (raw)
In-Reply-To: <20030305141123.GA16699@ally.lammerts.org>
From: Eric Lammerts <eric@lammerts.org>
Date: Wed, 5 Mar 2003 15:11:23 +0100
The reason is that (in af_packet.c) packet_notifier(NETDEV_DOWN) sets
sk->err to ENETDOWN, but packet_notifier(NETDEV_UP) doesn't clear it.
Is this behaviour deliberate?
Yes the behavior is deliberate. You want to be aware of the
event. Just because the opposite event has occurred afterwards
doesn't mean the first event didn't happen :-)
prev parent reply other threads:[~2003-03-06 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 14:11 [PATCH] wrong ENETDOWN in af_packet? Eric Lammerts
2003-03-06 18:31 ` 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=20030306.103142.58817243.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eric@lammerts.org \
--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).