| To: | eric@xxxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH] wrong ENETDOWN in af_packet? |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 06 Mar 2003 10:31:42 -0800 (PST) |
| Cc: | linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, alan@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20030305141123.GA16699@xxxxxxxxxxxxxxxxx> |
| References: | <20030305141123.GA16699@xxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Eric Lammerts <eric@xxxxxxxxxxxx> 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 in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Output on raw sockets ignores IP_DF when packet is bigger than pmtu, Sridhar Samudrala |
|---|---|
| Next by Date: | Make ipconfig.c work as a loadable module., Robin Holt |
| Previous by Thread: | [PATCH] wrong ENETDOWN in af_packet?, Eric Lammerts |
| Next by Thread: | [Bug] PPPoATM or ATM module problem with ADSL PCI Cards, Antonio Gallo |
| Indexes: | [Date] [Thread] [Top] [All Lists] |