From: sfel...@gmail.com Date: Wed, 12 Aug 2015 18:45:25 -0700 > From: Scott Feldman <sfel...@gmail.com> > > Rocker driver tracks arp_tbl neighs to resolve IPv4 route nexthops. The > driver uses NETEVENT_NEIGH_UPDATE for neigh adds and updates, but there is > no event when the neigh is removed from the device (such as when the device > goes admin down). This patches hooks ndo_neigh_destroy so the driver can > know when a neigh is removed from the device. In response, the driver will > purge the neigh entry from its internal tbl. > > I didn't find an in-tree users of ndo_neigh_destroy, so I'm not sure if > this ndo is vestigial or if there are out-of-tree users. In any case, it > does what I need here. An alternative design would be to generate > NETEVENT_NEIGH_UPDATE event when neigh is being destroyed, setting state to > NUD_NONE so driver knows neigh entry is dead. > > Signed-off-by: Scott Feldman <sfel...@gmail.com>
Also applied. ->ndo_neigh_destroy() is there simply for completeness. If anyone needed to manage neigh's they likely would have private software state assosciated with entries they would need to release when the neigh object is going away. -- 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
