netdev - Re: [PATCH] Disable router anycast address for /127 prefixes

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 01 Jul 2011 15:09:57 -0400
From:	Brian Haley <brian.haley@...com>
To:	Bjørn Mork <bjorn@...k.no>
CC:	netdev@...r.kernel.org
Subject: Re: [PATCH] Disable router anycast address for /127 prefixes

On 07/01/2011 02:26 PM, Bjørn Mork wrote:
> Brian Haley <brian.haley@...com> writes:
>> On 07/01/2011 07:22 AM, Bjørn Mork wrote:
>>> RFC 6164 requires that routers MUST disable Subnet-Router anycast
>>> for the prefix when /127 prefixes are used.
>>>
>>> Signed-off-by: Bjørn Mork <bjorn@...k.no>
>>> ---
>>
>>> @@ -1479,6 +1481,8 @@ static void addrconf_join_anycast(struct inet6_ifaddr *ifp)
>>>  static void addrconf_leave_anycast(struct inet6_ifaddr *ifp)
>>>  {
>>>  	struct in6_addr addr;
>>> +	if (ifp->prefix_len == 127) /* RFC 6164 */
>>> +		return;
>>>  	ipv6_addr_prefix(&addr, &ifp->addr, ifp->prefix_len);
>>>  	if (ipv6_addr_any(&addr))
>>>  		return;
>>
>> I'm not sure you'd need this part as there shouldn't be a /127 in the list to remove.
> 
> I don't understand exactly what you mean here.... 

If you never add an anycast address when the prefix length is 127, the address
wouldn't be there when you went to remove it.  In other words, the call to
__ipv6_dev_ac_dec() would return -ENOENT, which is ignored anyways.

It's not a common codepath so the two lines of code wouldn't hurt anything
I guess...

-Brian
--
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