tnl-neigh-cache: Force revalidation for a new neighbor entry.

When a new ARP or ND entry was added, the code failed to force revalidation. This commit fixes the problem. Reported-by: László Sürü <[email protected]> Reported-at: https://mail.openvswitch.org/pipermail/ovs-dev/2017-January/327788.html Tested-by: László Sürü <[email protected]> Signed-off-by: Ben Pfaff <[email protected]>
evelikov · Jan 20, 2017 · 6fd4b2a · 6fd4b2a
1 parent fafa41a
commit 6fd4b2a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 1 deletion.
diff --git a/AUTHORS.rst b/AUTHORS.rst
@@ -430,6 +430,7 @@ Konstantin Khorenko             [email protected]
 Kris zhang                      [email protected]
 Krishna Miriyala                [email protected]
 Krishna Mohan Elluru            [email protected]
+László Sürü                     [email protected]
 Len Gao                         [email protected]
 Logan Rosen                     [email protected]
 Luca Falavigna                  [email protected]

diff --git a/lib/tnl-neigh-cache.c b/lib/tnl-neigh-cache.c
@@ -126,8 +126,8 @@ tnl_neigh_set__(const char name[IFNAMSIZ], const struct in6_addr *dst,
             return;
         }
         tnl_neigh_delete(neigh);
-        seq_change(tnl_conf_seq);
     }
+    seq_change(tnl_conf_seq);
 
     neigh = xmalloc(sizeof *neigh);