diff options
author | Wei Yongjun <weiyongjun1@huawei.com> | 2016-09-05 16:06:31 +0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2016-09-06 14:17:49 -0700 |
commit | 751eb6b6042a596b0080967c1a529a9fe98dac1d (patch) | |
tree | 4b159ea0d70e6814be1c51e56bd1a8ee2da26a8f /MAINTAINERS | |
parent | 9d13744bb75078175ab49408f2abb980e4dbccc9 (diff) | |
download | linux-751eb6b6042a596b0080967c1a529a9fe98dac1d.tar.bz2 |
ipv6: addrconf: fix dev refcont leak when DAD failed
In general, when DAD detected IPv6 duplicate address, ifp->state
will be set to INET6_IFADDR_STATE_ERRDAD and DAD is stopped by a
delayed work, the call tree should be like this:
ndisc_recv_ns
-> addrconf_dad_failure <- missing ifp put
-> addrconf_mod_dad_work
-> schedule addrconf_dad_work()
-> addrconf_dad_stop() <- missing ifp hold before call it
addrconf_dad_failure() called with ifp refcont holding but not put.
addrconf_dad_work() call addrconf_dad_stop() without extra holding
refcount. This will not cause any issue normally.
But the race between addrconf_dad_failure() and addrconf_dad_work()
may cause ifp refcount leak and netdevice can not be unregister,
dmesg show the following messages:
IPv6: eth0: IPv6 duplicate address fe80::XX:XXXX:XXXX:XX detected!
...
unregister_netdevice: waiting for eth0 to become free. Usage count = 1
Cc: stable@vger.kernel.org
Fixes: c15b1ccadb32 ("ipv6: move DAD and addrconf_verify processing
to workqueue")
Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions