[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190904.153321.186858821162730720.davem@davemloft.net>
Date: Wed, 04 Sep 2019 15:33:21 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: zenczykowski@...il.com
Cc: maze@...gle.com, netdev@...r.kernel.org, dsahern@...il.com,
lorenzo@...gle.com
Subject: Re: [PATCH v2] net-ipv6: fix excessive RTF_ADDRCONF flag on
::1/128 local route (and others)
From: Maciej Żenczykowski <zenczykowski@...il.com>
Date: Mon, 2 Sep 2019 09:23:36 -0700
> From: Maciej Żenczykowski <maze@...gle.com>
>
> There is a subtle change in behaviour introduced by:
> commit c7a1ce397adacaf5d4bb2eab0a738b5f80dc3e43
> 'ipv6: Change addrconf_f6i_alloc to use ip6_route_info_create'
>
> Before that patch /proc/net/ipv6_route includes:
> 00000000000000000000000000000001 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000003 00000000 80200001 lo
>
> Afterwards /proc/net/ipv6_route includes:
> 00000000000000000000000000000001 80 00000000000000000000000000000000 00 00000000000000000000000000000000 00000000 00000002 00000000 80240001 lo
>
> ie. the above commit causes the ::1/128 local (automatic) route to be flagged with RTF_ADDRCONF (0x040000).
>
> AFAICT, this is incorrect since these routes are *not* coming from RA's.
>
> As such, this patch restores the old behaviour.
>
> Fixes: c7a1ce397adacaf5d4bb2eab0a738b5f80dc3e43
Please format your Fixes: tag properly next time, I fixed it up for you.
> Cc: David Ahern <dsahern@...il.com>
> Cc: Lorenzo Colitti <lorenzo@...gle.com>
> Signed-off-by: Maciej Żenczykowski <maze@...gle.com>
Applied and queued up for -stable.
Powered by blists - more mailing lists