summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorYing Xue <ying.xue@windriver.com>2015-05-15 07:53:21 +0300
committerDavid S. Miller <davem@davemloft.net>2015-05-16 04:20:16 +0300
commit1f9993f6825f9cb93f75f794b66e7428dfc72467 (patch)
tree90e8005805a0d73bbb3c401899930dbeb39ed914 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent86b5e7de07aa1abc87ecc40d2aca6070348e4469 (diff)
downloadlinux-1f9993f6825f9cb93f75f794b66e7428dfc72467.tar.xz
rocker: fix a neigh entry leak issue
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 <edumazet@google.com> Acked-by: Jiri Pirko <jiri@resnulli.us> Acked-by: Eric Dumazet <edumazet@google.com> Signed-off-by: Ying Xue <ying.xue@windriver.com> Acked-by: Jiri Pirko <jiri@resnulli.us> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions