From: Erik Kline <e...@google.com> Date: Mon, 18 May 2015 19:44:41 +0900
> [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 <e...@google.com> Please, in the future, put a proper subsystem prefix in the Subject line of your patch submissions. In this particular case "neigh: " would have been appropriate and is what I added when applying your patch. Applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
