From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Martin_Jab=C5=AFrek_=3Cmartin=2Ejaburek=40suse=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
fmancera@suse.de
Subject: Re: [PATCH net-next v3] selftests: net: add IPv4 and IPv6 address order check
Date: Thu, 17 Sep 2026 13:40:04 +0000 [thread overview]
Message-ID: <178965240488.3650140.11503348888989636421.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260914065848.10518-1-martin.jaburek@suse.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 14 Sep 2026 08:58:48 +0200 you wrote:
> Introduce the following new tests: `ipv4_verify_same_scope_addr_order`,
> `ipv4_verify_inter_scope_addr_order`, `ipv6_verify_same_scope_addr_order`,
> `ipv6_verify_inter_scope_addr_order` to check the ordering of a
> set of IP addresses after being inserted.
>
> The implementations of these protocols are inconsistent
> in regard to address ordering. IPv4 addresses stay in the
> same order as inserted while IPv6 addresses appear in
> reverse order. This inconsistency has prompted attempts
> to unify the ordering, so both protocols act the same
> (as IPv4). This however caused user-space regressions in
> certain applications, which relied on the order as it
> was prior to the change (particularly NetworkManager).
> A similar inconsistency occurs when inserting different
> scope addresses, where IPv4 puts link local ones before global
> and IPv6 does the opposite. Attempts were already made
> to unify this also, risking further regressions.
>
> [...]
Here is the summary with links:
- [net-next,v3] selftests: net: add IPv4 and IPv6 address order check
https://git.kernel.org/netdev/net-next/c/b8a6f2340999
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-17 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 6:58 [PATCH net-next v3] selftests: net: add IPv4 and IPv6 address order check Martin Jabůrek
2026-09-17 11:02 ` Fernando Fernandez Mancera
2026-09-17 13:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178965240488.3650140.11503348888989636421.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Martin_Jab=C5=AFrek_=3Cmartin=2Ejaburek=40suse=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox