[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20130801.163423.349667433630759733.davem@davemloft.net>
Date: Thu, 01 Aug 2013 16:34:23 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: fan.du@...driver.com
Cc: yoshfuji@...ux-ipv6.org, jmorris@...ei.org,
hannes@...essinduktion.org, vyasevich@...il.com,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next] ipv6: bump genid when delete/add address
From: Fan Du <fan.du@...driver.com>
Date: Thu, 1 Aug 2013 17:44:44 +0800
> Server Client
> 2001:1::803/64 <-> 2001:1::805/64
> 2001:2::804/64 <-> 2001:2::806/64
>
> Server side fib binary tree looks like this:
>
> (2001:/64)
> /
> /
> ffff88002103c380
> / \
> (2) / \
> (2001::803/128) ffff880037ac07c0
> / \
> / \ (3)
> ffff880037ac0640 (2001::806/128)
> / \
> (1) / \
> (2001::804/128) (2001::805/128)
>
> Delete 2001::804/64 won't cause prefix route deleted as well as rt in (3)
> destinate to 2001::806 with source address as 2001::804/64. That's because
> 2001::803/64 is still alive, which make onlink=1 in ipv6_del_addr, this is
> where the substantial difference between same prefix configuration and
> different prefix configuration :) So packet are still transmitted out to
> 2001::806 with source address as 2001::804/64.
>
> So bump genid will clear rt in (3), and up layer protocol will eventually
> find the right one for themselves.
>
> This problem arised from the discussion in here:
> http://marc.info/?l=linux-netdev&m=137404469219410&w=4
>
> Signed-off-by: Fan Du <fan.du@...driver.com>
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists