summaryrefslogtreecommitdiffstats
path: root/net/ipv4/tcp_output.c
diff options
context:
space:
mode:
authorErik Kline2015-05-18 12:44:41 +0200
committerDavid S. Miller2015-05-21 22:52:17 +0200
commit765c9c639fbb132af0cafc6e1da22fe6cea26bb8 (patch)
tree3a197a9708a23ffafcee827225366c8f3ecbbe49 /net/ipv4/tcp_output.c
parentip: remove unused function prototype (diff)
downloadkernel-qcow2-linux-765c9c639fbb132af0cafc6e1da22fe6cea26bb8.tar.gz
kernel-qcow2-linux-765c9c639fbb132af0cafc6e1da22fe6cea26bb8.tar.xz
kernel-qcow2-linux-765c9c639fbb132af0cafc6e1da22fe6cea26bb8.zip
neigh: Better handling of transition to NUD_PROBE state
[1] When entering NUD_PROBE state via neigh_update(), perhaps received from userspace, correctly (re)initialize the probes count to zero. This is useful for forcing revalidation of a neighbor (for example if the host is attempting to do DNA [IPv4 4436, IPv6 6059]). [2] Notify listeners when a neighbor goes into NUD_PROBE state. By sending notifications on entry to NUD_PROBE state listeners get more timely warnings of imminent connectivity issues. The current notifications on entry to NUD_STALE have somewhat limited usefulness: NUD_STALE is a perfectly normal state, as is NUD_DELAY, whereas notifications on entry to NUD_FAILURE come after a neighbor reachability problem has been confirmed (typically after three probes). Signed-off-by: Erik Kline <ek@google.com> Acked-By: Lorenzo Colitti <lorenzo@google.com> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/tcp_output.c')
0 files changed, 0 insertions, 0 deletions