Netdev List
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: "Íñigo Huguet" <ihuguet@redhat.com>
Cc: 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,
	kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
	idosch@nvidia.com, dsahern@kernel.org,
	Chris Adams <linux@cmadams.net>,
	David Gibson <david@gibson.dropbear.id.au>,
	Beniamino Galvani <bgalvani@redhat.com>,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	Andrew Lunn <andrew@lunn.ch>,
	regressions@lists.linux.dev
Subject: Re: [PATCH net v2] Revert "ipv6: preserve insertion order for same-scope addresses"
Date: Wed, 3 Jun 2026 19:27:17 +1000	[thread overview]
Message-ID: <f0df3ca1-793d-4985-995c-50227fd5123d@kernel.org> (raw)
In-Reply-To: <CACT4oueJ3GsVvnWcZHgYVL-fCjpt5nOw+2=0BTmiz-9xKY4B0w@mail.gmail.com>

Hi Íñigo,

On 03/06/2026 16:53, Íñigo Huguet wrote:
> On Wed, Jun 3, 2026 at 7:46 AM Matthieu Baerts <matttbe@kernel.org> wrote:
>> I guess it is safer not to break UAPI and not reapplying the patch,
>> especially when there is no clear way to know which order is taken by
>> the kernel.
>>
>> What about clearly stating that the default order is "random", except
>> when an additional flag is set to sort them chronologically or the opposite?
> 
> Stating that the order is "random" implies that someone will change
> the default insertion order in the future, as the documentation says
> that it's not UAPI. So they'll cause the UAPI breakage that we are
> trying to avoid now. Moreover, if we consider the default order
> "random" and state that userspace programs must not rely on it, why
> can't we change it now?

I was only suggesting "random", simply to force userspace programs to
ask for a specific order when the order matters. But also to avoid
having to describe the current order, which is different in v4 and v6
for entries of the same scope.

I know the order is not random, and even if it is confusing, I don't
think we can change it without breaking stuff.

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  parent reply	other threads:[~2026-06-03  9:27 UTC|newest]

Thread overview: 23+ 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 [this message]
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-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=f0df3ca1-793d-4985-995c-50227fd5123d@kernel.org \
    --to=matttbe@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=bgalvani@redhat.com \
    --cc=davem@davemloft.net \
    --cc=david@gibson.dropbear.id.au \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=fmancera@suse.de \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=ihuguet@redhat.com \
    --cc=justin.iurman@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@cmadams.net \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sbrivio@redhat.com \
    --cc=yuhuang@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