[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANsz47=_bwrHa-RChtbZyBTJxrM8MtCtrJm_x-gRUaw2Ndr_yw@mail.gmail.com>
Date: Fri, 28 Nov 2025 14:38:58 +0800
From: Yumei Huang <yuhuang@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, sbrivio@...hat.com,
david@...son.dropbear.id.au, davem@...emloft.net, dsahern@...nel.org,
edumazet@...gle.com, pabeni@...hat.com, horms@...nel.org
Subject: Re: [PATCH] ipv6: preserve insertion order for same-scope addresses
On Wed, Nov 26, 2025 at 10:58 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Wed, 26 Nov 2025 16:37:14 +0800 Yumei Huang wrote:
> > IPv6 addresses with the same scope were returned in reverse insertion
> > order, unlike IPv4. For example, when adding a -> b -> c, the list was
> > reported as c -> b -> a, while IPv4 preserved the original order.
> >
> > This patch aligns IPv6 address ordering with IPv4 for consistency.
>
> This breaks the ioam6.sh test:
> https://netdev-3.bots.linux.dev/vmksft-net-dbg/results/402461/16-ioam6-sh/stdout
> https://netdev-3.bots.linux.dev/vmksft-net/results/402461/14-ioam6-sh/stdout
Thanks for catching this. The error can be fixed by just swaping the
two lines of adding addresses for veth0 in ioam_node_alpha netns. I
will fix it in v2. Thanks!
> --
> pw-bot: cr
>
--
Thanks,
Yumei Huang
Powered by blists - more mailing lists