[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C76DB17.8080601@candelatech.com>
Date: Thu, 26 Aug 2010 14:22:31 -0700
From: Ben Greear <greearb@...delatech.com>
To: Brian Haley <brian.haley@...com>
CC: David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [net-next] ipv6: Enable netlink notification for tentative addresses.
On 08/26/2010 12:57 PM, Brian Haley wrote:
> On 08/26/2010 02:50 PM, Ben Greear wrote:
>> @@ -697,9 +698,10 @@ ipv6_add_addr(struct inet6_dev *idev, const struct
>> in6_addr *addr, int pfxlen,
>> out2:
>> rcu_read_unlock_bh();
>>
>> - if (likely(err == 0))
>> + if (likely(err == 0)) {
>> atomic_notifier_call_chain(&inet6addr_chain, NETDEV_UP,
>> ifa);
>> - else {
>> + inet6_ifa_notify(RTM_NEWADDR, ifa);
>> + } else {
>> kfree(ifa);
>> ifa = ERR_PTR(err);
>> }
>
> This will generate two messages in some cases, for example, when lo is
> configured, or a SIT tunnel is added, see add_addr() in addrconf.c.
Would that cause any problem though? It seems a common pattern to
send 'new-foo' netlink messages when some value in foo changes.
Thanks,
Ben
--
Ben Greear <greearb@...delatech.com>
Candela Technologies Inc http://www.candelatech.com
--
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