vxlan: fix check for migration of static entry

The check introduced by:
	commit dcc5867f81f69dac5d714063e1cf95e008899820
	Author: stephen hemminger <stephen@networkplumber.org>
	Date:   Mon Jun 17 12:09:58 2013 -0700

	    vxlan: only migrate dynamic FDB entries

was not correct because it is checking flag about type of FDB
entry, rather than the state (dynamic versus static). The confusion
arises because vxlan is reusing values from bridge, and bridge is
reusing values from neighbour table, and easy to get lost in translation.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c
index dda997a0102c39175be955077f64a79461c3cfbb..57325f356d4f125421bfa297a4beb2302c5f194b 100644 (file)
--- a/drivers/net/vxlan.c
+++ b/drivers/net/vxlan.c
@@ -579,7 +579,7 @@ static bool vxlan_snoop(struct net_device *dev,
                        return false;
 
                /* Don't migrate static entries, drop packets */
-               if (!(f->flags & NTF_SELF))
+               if (f->state & NUD_NOARP)
                        return true;
 
                if (net_ratelimit())