diff options
author | Erik Kline <ek@google.com> | 2016-02-12 14:24:08 +0100 |
---|---|---|
committer | Gerrit Code Review <gerrit@cyanogenmod.org> | 2016-02-14 14:11:57 -0800 |
commit | b1ce5b792e0c6bddb9012dbbff63cfcc3a4aaf87 (patch) | |
tree | 9afd9fab1bbd2c950eeec8930a945398777db42a /fs/ext4 | |
parent | 79130f59981085bac73777da127546e427eaccdf (diff) | |
download | kernel_samsung_smdk4412-b1ce5b792e0c6bddb9012dbbff63cfcc3a4aaf87.zip kernel_samsung_smdk4412-b1ce5b792e0c6bddb9012dbbff63cfcc3a4aaf87.tar.gz kernel_samsung_smdk4412-b1ce5b792e0c6bddb9012dbbff63cfcc3a4aaf87.tar.bz2 |
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).
[Cherry-pick of upstream 765c9c639fbb132af0cafc6e1da22fe6cea26bb8]
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>
Change-Id: I3a48f267a1bf752daeb3ff8a28de926ac66f5ad8
Diffstat (limited to 'fs/ext4')
0 files changed, 0 insertions, 0 deletions