linux-stable.git/net/ipv6/ndisc.c, branch linux-3.1.y Linux kernel stable tree net: Abstract dst->neighbour accesses behind helpers. 2011-07-18T06:11:35+00:00 David S. Miller davem@davemloft.net 2011-07-18T06:09:49+00:00 69cce1d1404968f78b177a0314f5822d5afdbbfb dst_{get,set}_neighbour() Signed-off-by: David S. Miller <davem@davemloft.net> 
dst_{get,set}_neighbour()

Signed-off-by: David S. Miller <davem@davemloft.net>
ipv6: Get rid of rt6i_nexthop macro. 2011-07-18T06:11:35+00:00 David S. Miller davem@davemloft.net 2011-07-18T03:06:13+00:00 9cbb7ecbcff85077bb12301aaf4c9b5a56c5993d It just makes it harder to see 1) what the code is doing and 2) grep for all users of dst{->,.}neighbour Signed-off-by: David S. Miller <davem@davemloft.net> 
It just makes it harder to see 1) what the code is doing
and 2) grep for all users of dst{->,.}neighbour

Signed-off-by: David S. Miller <davem@davemloft.net>
neigh: Pass neighbour entry to output ops. 2011-07-18T06:11:17+00:00 David S. Miller davem@davemloft.net 2011-07-17T20:34:11+00:00 8f40b161de4f27402b4c0659ad2ae83fad5a0cdd This will get us closer to being able to do "neigh stuff" completely independent of the underlying dst_entry for protocols (ipv4/ipv6) that wish to do so. We will also be able to make dst entries neigh-less. Signed-off-by: David S. Miller <davem@davemloft.net> 
This will get us closer to being able to do "neigh stuff"
completely independent of the underlying dst_entry for
protocols (ipv4/ipv6) that wish to do so.

We will also be able to make dst entries neigh-less.

Signed-off-by: David S. Miller <davem@davemloft.net>
neigh: Kill ndisc_ops->queue_xmit 2011-07-17T01:30:59+00:00 David S. Miller davem@davemloft.net 2011-07-17T01:06:24+00:00 542d4d685febf3110d1a08d0bcb9f6ef060b76f7 It is always dev_queue_xmit(). Signed-off-by: David S. Miller <davem@davemloft.net> 
It is always dev_queue_xmit().

Signed-off-by: David S. Miller <davem@davemloft.net>
neigh: Kill neigh_ops->hh_output 2011-07-17T00:39:57+00:00 David S. Miller davem@davemloft.net 2011-07-17T00:39:57+00:00 47ec132a40d788d45e2f088545dea68798034dab It's always dev_queue_xmit(). Signed-off-by: David S. Miller <davem@davemloft.net> 
It's always dev_queue_xmit().

Signed-off-by: David S. Miller <davem@davemloft.net>
ipv4, ipv6, bonding: Restore control over number of peer notifications 2011-04-29T19:44:11+00:00 Ben Hutchings bhutchings@solarflare.com 2011-04-26T15:25:52+00:00 ad246c992bea6d33c6421ba1f03e2b405792adf9 For backward compatibility, we should retain the module parameters and sysfs attributes to control the number of peer notifications (gratuitous ARPs and unsolicited NAs) sent after bonding failover. Also, it is possible for failover to take place even though the new active slave does not have link up, and in that case the peer notification should be deferred until it does. Change ipv4 and ipv6 so they do not automatically send peer notifications on bonding failover. Change the bonding driver to send separate NETDEV_NOTIFY_PEERS notifications when the link is up, as many times as requested. Since it does not directly control which protocols send notifications, make num_grat_arp and num_unsol_na aliases for a single parameter. Bump the bonding version number and update its documentation. Signed-off-by: Ben Hutchings <bhutchings@solarflare.com> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com> Acked-by: Brian Haley <brian.haley@hp.com> Signed-off-by: David S. Miller <davem@davemloft.net> 
For backward compatibility, we should retain the module parameters and
sysfs attributes to control the number of peer notifications
(gratuitous ARPs and unsolicited NAs) sent after bonding failover.
Also, it is possible for failover to take place even though the new
active slave does not have link up, and in that case the peer
notification should be deferred until it does.

Change ipv4 and ipv6 so they do not automatically send peer
notifications on bonding failover.

Change the bonding driver to send separate NETDEV_NOTIFY_PEERS
notifications when the link is up, as many times as requested.  Since
it does not directly control which protocols send notifications, make
num_grat_arp and num_unsol_na aliases for a single parameter.  Bump
the bonding version number and update its documentation.

Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
Acked-by: Brian Haley <brian.haley@hp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
inet: constify ip headers and in6_addr 2011-04-22T18:04:14+00:00 Eric Dumazet eric.dumazet@gmail.com 2011-04-22T04:53:02+00:00 b71d1d426d263b0b6cb5760322efebbfc89d4463 Add const qualifiers to structs iphdr, ipv6hdr and in6_addr pointers where possible, to make code intention more obvious. Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> 
Add const qualifiers to structs iphdr, ipv6hdr and in6_addr pointers
where possible, to make code intention more obvious.

Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
bonding, ipv4, ipv6, vlan: Handle NETDEV_BONDING_FAILOVER like NETDEV_NOTIFY_PEERS 2011-04-18T06:36:03+00:00 Ben Hutchings bhutchings@solarflare.com 2011-04-15T13:47:51+00:00 7c89943236750537d26421d9bbb6f6575e2d1e1b It is undesirable for the bonding driver to be poking into higher level protocols, and notifiers provide a way to avoid that. This does mean removing the ability to configure reptitition of gratuitous ARPs and unsolicited NAs. Signed-off-by: Ben Hutchings <bhutchings@solarflare.com> Signed-off-by: David S. Miller <davem@davemloft.net> 
It is undesirable for the bonding driver to be poking into higher
level protocols, and notifiers provide a way to avoid that.  This does
mean removing the ability to configure reptitition of gratuitous ARPs
and unsolicited NAs.

Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
ipv6: Send unsolicited neighbour advertismements when notified 2011-04-18T06:35:16+00:00 Ben Hutchings bhutchings@solarflare.com 2011-04-15T13:46:02+00:00 f47b94646f30529624c82ab0f9cd5bd3f25ef9d2 The NETDEV_NOTIFY_PEERS notifier is a request to send such advertisements following migration to a different physical link, e.g. virtual machine migration. Signed-off-by: Ben Hutchings <bhutchings@solarflare.com> Signed-off-by: David S. Miller <davem@davemloft.net> 
The NETDEV_NOTIFY_PEERS notifier is a request to send such
advertisements following migration to a different physical link,
e.g. virtual machine migration.

Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
ipv6: ignore looped-back NA while dad is running 2011-04-15T22:43:55+00:00 Daniel Walter sahne@0x90.at 2011-04-13T21:09:25+00:00 bd015928bb1713691068c4d0d159afccbaf0f8c0 [ipv6] Ignore looped-back NAs while in Duplicate Address Detection If we send an unsolicited NA shortly after bringing up an IPv6 address, the duplicate address detection algorithm fails and the ip stays in tentative mode forever. This is due a missing check if the NA is looped-back to us. Signed-off-by: Daniel Walter <dwalter@barracuda.com> Signed-off-by: David S. Miller <davem@davemloft.net> 
[ipv6] Ignore looped-back NAs while in Duplicate Address Detection

If we send an unsolicited NA shortly after bringing up an
IPv6 address, the duplicate address detection algorithm
fails and the ip stays in tentative mode forever.
This is due a missing check if the NA is looped-back to us.

Signed-off-by: Daniel Walter <dwalter@barracuda.com>
Signed-off-by: David S. Miller <davem@davemloft.net>