[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1e99ece5-3ee6-4446-886a-ddc708aa8e0d@6wind.com>
Date: Tue, 18 Feb 2025 09:43:40 +0100
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: David Ahern <dsahern@...nel.org>, Eric Dumazet <edumazet@...gle.com>,
"David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Cc: netdev@...r.kernel.org, Paul Ripke <stix@...gle.com>,
Simon Horman <horms@...nel.org>, eric.dumazet@...il.com
Subject: Re: [PATCH net-next 2/2] ipv6: fix blackhole routes
Le 12/02/2025 à 19:00, David Ahern a écrit :
> On 2/12/25 9:43 AM, Eric Dumazet wrote:
>> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
>> index 78362822b9070df138a0724dc76003b63026f9e2..335cdbfe621e2fc4a71badf4ff834870638d5e13 100644
>> --- a/net/ipv6/route.c
>> +++ b/net/ipv6/route.c
>> @@ -1048,7 +1048,7 @@ static const int fib6_prop[RTN_MAX + 1] = {
>> [RTN_BROADCAST] = 0,
>> [RTN_ANYCAST] = 0,
>> [RTN_MULTICAST] = 0,
>> - [RTN_BLACKHOLE] = -EINVAL,
>> + [RTN_BLACKHOLE] = 0,
>> [RTN_UNREACHABLE] = -EHOSTUNREACH,
>> [RTN_PROHIBIT] = -EACCES,
>> [RTN_THROW] = -EAGAIN,
>
> EINVAL goes back to ef2c7d7b59708 in 2012, so this is a change in user
> visible behavior. Also this will make ipv6 deviate from ipv4:
>
> [RTN_BLACKHOLE] = {
> .error = -EINVAL,
> .scope = RT_SCOPE_UNIVERSE,
> },
Yes, if I remember well, to be consistent I mimicked what existed in IPv4. I
never found a good answer to why 'EINVAL' :)
Nicolas
Powered by blists - more mailing lists