netdev - Re: [RFC PATCH next] ipv6: do not send RTM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 06 Jan 2017 15:39:50 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     mahesh@...dewar.net
Cc:     netdev@...r.kernel.org, maheshb@...gle.com,
        yoshfuji@...ux-ipv6.org, kaber@...sh.net,
        hannes@...essinduktion.org
Subject: Re: [RFC PATCH next] ipv6: do not send RTM_DELADDR for tentative
 addresses

From: Mahesh Bandewar <mahesh@...dewar.net>
Date: Wed,  4 Jan 2017 15:01:01 -0800

> From: Mahesh Bandewar <maheshb@...gle.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@...gle.com>

This makes a lot of sense, applied, thanks!