Subject: Re: [PATCH] IPv6: fix anycast address ref count leakage

From: Stephen Hemminger <[email-masked]>
Date: Thu, 25 Feb 2010 16:54:52 -0800

On Thu, 25 Feb 2010 15:57:07 -0800
Stephen Hemminger <[email-masked]> wrote:

> The recent change in net-next to keep IPv6 address can lead to device
> hanging with unresolved refcount on removal. The issue is that the conversion
> of address from permanent to temporary needs to notify the anycast list
> code to clean up it's ref count. Also, want to tell other uses of IPv6
> (bonding/sctp) that the address is no longer available.
> 
> The fix is to notify like a regular delete.  When link comes back, DAD
> runs and will notify with NETDEV_UP that address is back.
> 
> The decrement of idev refcount when cleaning up addrconf_hash, should
> never cause address to be freed; therefore it can use __in6_ifa_put.
> 
> The timer cleanup should be done when address deletion is done
> in second loop.
> 
> Signed-off-by: Stephen Hemminger <[email-masked]>
> 

Wait till I split/revise this one; it has a problem.

--