From: David Miller <davem@davemloft.net>
To: mahesh@bandewar.net
Cc: netdev@vger.kernel.org, maheshb@google.com,
yoshfuji@linux-ipv6.org, kaber@trash.net,
hannes@stressinduktion.org
Subject: Re: [RFC PATCH next] ipv6: do not send RTM_DELADDR for tentative addresses
Date: Fri, 06 Jan 2017 15:39:50 -0500 (EST) [thread overview]
Message-ID: <20170106.153950.509531386949440475.davem@davemloft.net> (raw)
In-Reply-To: <20170104230101.17470-1-mahesh@bandewar.net>
From: Mahesh Bandewar <mahesh@bandewar.net>
Date: Wed, 4 Jan 2017 15:01:01 -0800
> From: Mahesh Bandewar <maheshb@google.com>
>
> RTM_NEWADDR notification is sent when IFA_F_TENTATIVE is cleared from
> the address. So if the address is added and deleted before DAD probes
> completes, the RTM_DELADDR will be sent for which there was no
> RTM_NEWADDR causing asymmetry in notification. However if the same
> logic is used while sending RTM_DELADDR notification, this asymmetry
> can be avoided.
>
> Signed-off-by: Mahesh Bandewar <maheshb@google.com>
This makes a lot of sense, applied, thanks!
prev parent reply other threads:[~2017-01-06 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 23:01 [RFC PATCH next] ipv6: do not send RTM_DELADDR for tentative addresses Mahesh Bandewar
2017-01-06 20:39 ` David Miller [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=20170106.153950.509531386949440475.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=kaber@trash.net \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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