[Top] [All Lists]

Re: Bug in ipv6_ifa_notify?

To: "David S. Miller" <davem@xxxxxxxxxxxxx>, Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>, YOSHIFUJI Hideaki <yoshfuji@xxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx
Subject: Re: Bug in ipv6_ifa_notify?
From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 9 Nov 2004 07:37:41 +1100
In-reply-to: <20041108121040.GA3618@xxxxxxxxxxxxxxxxxxx>
References: <20041108061529.GA1774@xxxxxxxxxxxxxxxxxxx> <20041108073441.GA2200@xxxxxxxxxxxxxxxxxxx> <20041108121040.GA3618@xxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6+20040722i
On Mon, Nov 08, 2004 at 11:10:40PM +1100, herbert wrote:
> On Mon, Nov 08, 2004 at 06:34:41PM +1100, herbert wrote:
> > 
> > RTM_DELADDR will call ip6_del_rt which will free the rt using
> > dst_free.  Since it is still referenced it gets put on the gc
> > list.  The next RTM_NEWADDR will put it back in the table.
> > From this point onwards anything that gets linked after it will
> > be on the gc list!
> Actually, address objects dont't seem to be kept across interface
> down/up operations, so this probably can't happen...

Well I've found a way for this to occur, but I must say that it is
fairly unlikely.  When you bring the interface down, addrconf_ifdown
will try to to delete the addrconf timer and then notify DELADDR.
Since it doesn't wait for the timer to complete, it might still be
executing.  Therefore it is possible to have a NEWADDR after a DELADDR
Visit Openswan at
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page:
PGP Key:

<Prev in Thread] Current Thread [Next in Thread>