[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<176774760977.2183630.3799089848817482368.git-patchwork-notify@kernel.org>
Date: Wed, 07 Jan 2026 01:00:09 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Yumei Huang <yuhuang@...hat.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, sbrivio@...hat.com,
david@...son.dropbear.id.au, davem@...emloft.net, dsahern@...nel.org,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
justin.iurman@...ege.be, shuah@...nel.org
Subject: Re: [PATCH net-next v2] ipv6: preserve insertion order for same-scope
addresses
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Sun, 4 Jan 2026 11:23:57 +0800 you wrote:
> IPv6 addresses with the same scope are returned in reverse insertion
> order, unlike IPv4. For example, when adding a -> b -> c, the list is
> reported as c -> b -> a, while IPv4 preserves the original order.
>
> This behavior causes:
>
> a. When using `ip -6 a save` and `ip -6 a restore`, addresses are restored
> in the opposite order from which they were saved. See example below
> showing addresses added as 1::1, 1::2, 1::3 but displayed and saved
> in reverse order.
>
> [...]
Here is the summary with links:
- [net-next,v2] ipv6: preserve insertion order for same-scope addresses
https://git.kernel.org/netdev/net-next/c/cb3de96eea66
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists