ipv6: fib: fix fib dump restart
authorKumar Sundararajan <kumar@fb.com>
Thu, 24 Apr 2014 13:48:53 +0000 (09:48 -0400)
committerBen Hutchings <ben@decadent.org.uk>
Fri, 6 Mar 2015 00:39:20 +0000 (00:39 +0000)
commit4c5bc740767e3dc3e07da9bbe1738222158ff87f
treec3fe0e509fc7bb785432d5e9e4a051fe03c40a39
parentee558c90853a71c318a2d15ba2e747623fa0af86
ipv6: fib: fix fib dump restart

commit 1c2658545816088477e91860c3a645053719cb54 upstream.

When the ipv6 fib changes during a table dump, the walk is
restarted and the number of nodes dumped are skipped. But the existing
code doesn't advance to the next node after a node is skipped. This can
cause the dump to loop or produce lots of duplicates when the fib
is modified during the dump.

This change advances the walk to the next node if the current node is
skipped after a restart.

Signed-off-by: Kumar Sundararajan <kumar@fb.com>
Signed-off-by: Chris Mason <clm@fb.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
net/ipv6/ip6_fib.c