From: Ben Greear <greearb@candelatech.com>
To: Brian Haley <brian.haley@hp.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [net-next] ipv6: Enable netlink notification for tentative addresses.
Date: Thu, 26 Aug 2010 14:22:31 -0700 [thread overview]
Message-ID: <4C76DB17.8080601@candelatech.com> (raw)
In-Reply-To: <4C76C73F.4080206@hp.com>
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@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-08-26 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 18:26 [net-next] ipv6: Enable netlink notification for tentative addresses Ben Greear
2010-08-26 4:24 ` David Miller
2010-08-26 18:50 ` Ben Greear
2010-08-26 19:57 ` Brian Haley
2010-08-26 20:18 ` David Miller
2010-08-26 21:19 ` Ben Greear
2010-08-26 21:27 ` David Miller
2010-08-27 4:24 ` Ben Greear
2010-08-26 21:22 ` Ben Greear [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C76DB17.8080601@candelatech.com \
--to=greearb@candelatech.com \
--cc=brian.haley@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).