From: Ihar Hrachyshka <ihrac...@redhat.com> Date: Tue, 9 May 2017 17:06:05 -0700
> Sometimes neigh_update calls won't touch neither lladdr nor state, for > example if an update arrives in locktime interval. Then we effectively > ignore the update request, bailing out of touching the neigh entry, > except that we still bump its timestamps. So, in order to understand this, one has to know that the ->updated value is tested by the protocol specific neigh code, which in turn will thus influence whether NEIGH_UPDATE_F_OVERRIDE gets set in the call to neigh_update() or not. Please update your commit message to explain that this is how the locktime mechanism influences neigh_update()'s behavior. Thank you.
