From: Jakub Kicinski <kuba@kernel•org>
To: Ido Schimmel <idosch@nvidia•com>
Cc: David Gibson <david@gibson•dropbear.id.au>,
Stefano Brivio <sbrivio@redhat•com>,
Fernando Fernandez Mancera <fmancera@suse•de>,
netdev@vger•kernel.org, yuhuang@redhat•com,
justin.iurman@gmail•com, horms@kernel•org, pabeni@redhat•com,
edumazet@google•com, davem@davemloft•net, dsahern@kernel•org,
Chris Adams <linux@cmadams•net>,
Beniamino Galvani <bgalvani@redhat•com>,
Thorsten Leemhuis <regressions@leemhuis•info>,
Andrew Lunn <andrew@lunn•ch>,
ihuguet@redhat•com, regressions@lists•linux.dev
Subject: Re: IPv6 address insertion order (was Re: [PATCH net v2] Revert "ipv6: preserve insertion order for same-scope addresses")
Date: Thu, 4 Jun 2026 15:55:35 -0700 [thread overview]
Message-ID: <20260604155535.4662a95b@kernel.org> (raw)
In-Reply-To: <20260604183909.GA877115@shredder>
On Thu, 4 Jun 2026 21:39:09 +0300 Ido Schimmel wrote:
> Given the above, my preference would be #3 -> #2 -> #1. The first two
> options expose the same capability to user space, so #1 doesn't buy us
> anything over #2, except a bit less code, but we risk introducing a
> regression.
>
> Between #2 and #3, production software can't drop the fallback even if
> we implement #2, yet #2 requires us to maintain uAPI forever. I think we
> should accept that the divergence between IPv4 and IPv6 is not ideal,
> but at least it's predictable and dependable (Fernando is working on a
> ksft and documentation).
+1 to this, FWIW
next prev parent reply other threads:[~2026-06-04 22:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 11:23 [PATCH net v2] Revert "ipv6: preserve insertion order for same-scope addresses" Fernando Fernandez Mancera
2026-05-29 11:41 ` Stefano Brivio
2026-05-29 11:45 ` Fernando Fernandez Mancera
2026-05-29 12:06 ` Chris Adams
2026-06-01 2:03 ` Matthieu Baerts
2026-06-01 13:35 ` Stefano Brivio
2026-06-01 14:01 ` Íñigo Huguet
2026-06-01 14:22 ` Thorsten Leemhuis
2026-06-03 5:46 ` Matthieu Baerts
2026-06-03 6:53 ` Íñigo Huguet
2026-06-03 7:17 ` Thorsten Leemhuis
2026-06-03 7:29 ` Fernando Fernandez Mancera
2026-06-03 8:00 ` Ido Schimmel
2026-06-03 8:06 ` Fernando Fernandez Mancera
2026-06-03 9:27 ` Matthieu Baerts
2026-06-03 8:02 ` David Gibson
2026-06-02 6:44 ` IPv6 address insertion order (was Re: [PATCH net v2] Revert "ipv6: preserve insertion order for same-scope addresses") David Gibson
2026-06-02 12:46 ` Andrew Lunn
2026-06-03 1:56 ` David Gibson
2026-06-02 13:21 ` Ido Schimmel
2026-06-03 2:34 ` David Gibson
2026-06-03 7:47 ` Ido Schimmel
2026-06-03 15:45 ` Stefano Brivio
2026-06-04 1:26 ` David Gibson
2026-06-04 18:39 ` Ido Schimmel
2026-06-04 22:55 ` Jakub Kicinski [this message]
2026-06-05 10:13 ` Stefano Brivio
2026-06-03 15:47 ` Nicolas Dichtel
2026-05-29 20:20 ` [PATCH net v2] Revert "ipv6: preserve insertion order for same-scope addresses" patchwork-bot+netdevbpf
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=20260604155535.4662a95b@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=bgalvani@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=fmancera@suse$(echo .)de \
--cc=horms@kernel$(echo .)org \
--cc=idosch@nvidia$(echo .)com \
--cc=ihuguet@redhat$(echo .)com \
--cc=justin.iurman@gmail$(echo .)com \
--cc=linux@cmadams$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=regressions@leemhuis$(echo .)info \
--cc=regressions@lists$(echo .)linux.dev \
--cc=sbrivio@redhat$(echo .)com \
--cc=yuhuang@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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