From: Ying Xue <[email protected]> Date: Fri, 15 May 2015 09:33:25 +0800
> Once we get a neighbour through looking up arp cache or creating a > new one in rocker_port_ipv4_resolve(), the neighbour's refcount is > already taken. But as we don't put the refcount again after it's > used, this makes the neighbour entry leaked. > > Suggested-by: Eric Dumazet <[email protected]> > Acked-by: Jiri Pirko <[email protected]> > Signed-off-by: Ying Xue <[email protected]> > --- > v2: > Add the checking of return value of neigh_create() with IS_ERR() > to avoid another crash, which is suggested by Eric Dumazet. Doesn't this leak exist in the 'net' tree? If so, why are you targetting such a bug fix for 'net-next'? -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
