From: Chris Adams <linux@cmadams•net>
To: Jakub Kicinski <kuba@kernel•org>
Cc: netdev@vger•kernel.org, Yumei Huang <yuhuang@redhat•com>,
Fernando Fernandez Mancera <fmancera@suse•de>,
Ido Schimmel <idosch@idosch•org>
Subject: Re: Problem with IPv6 privacy addresses in 7.0
Date: Wed, 27 May 2026 16:13:56 -0500 [thread overview]
Message-ID: <20260527211356.GA16443@cmadams.net> (raw)
In-Reply-To: <20260526183122.348e44e7@kernel.org>
Once upon a time, Jakub Kicinski <kuba@kernel•org> said:
> On Tue, 26 May 2026 20:06:41 -0500 Chris Adams wrote:
> > > Hi! Adding more people to CC. Do you know if you upgraded from 6.18
> > > or 6.19?
> >
> > It was 6.19 to 7.0.
> >
> > > Would you be able to try testing with some commits reverted?
> > > On a quick look the candidates would be:
> > >
> > > cb3de96eea66 ("ipv6: preserve insertion order for same-scope addresses")
> >
> > It's this one.
>
> Phew, the second one was mine :)
>
> > I figured out that it happens after stopping a VM (and I usually
> > start/stop a VM for a bit in the morning, which is why it happened more
> > than once). So I set up a VM with a nested VM, running up-to-date
> > Fedora 44, and then was able to bisect pretty easily, and it landed on
> > this commit.
> >
> > Fedora is using NetworkManager, and IIRC NM does some part of privacy
> > address management (right?). NM didn't change, so maybe this commit is
> > confusing something in NM?
>
> Sounds plausible, pretty sure we knew this commit was risky to begin
> with, but we had no direct proof that it'd break real life users.
>
> Revert is the right course of action here. Would you be willing/able
> to send the revert with your problem description and a Fixes tag
> pointing to the reverted commit?
So... I'm not very git-fluent and haven't submitted a kernel patch in
many years, so really am not sure of the necessary/proper steps.
--
Chris Adams <linux@cmadams•net>
next prev parent reply other threads:[~2026-05-27 21:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 13:53 Problem with IPv6 privacy addresses in 7.0 Chris Adams
2026-05-27 0:57 ` Jakub Kicinski
2026-05-27 1:06 ` Chris Adams
2026-05-27 1:31 ` Jakub Kicinski
2026-05-27 21:13 ` Chris Adams [this message]
2026-05-27 21:16 ` Fernando Fernandez Mancera
2026-05-27 21:51 ` Jakub Kicinski
2026-05-27 21:51 ` Chris Adams
2026-05-27 21:59 ` Fernando Fernandez Mancera
2026-05-27 23:07 ` Jakub Kicinski
2026-05-28 5:38 ` Stefano Brivio
2026-05-28 10:46 ` Fernando Fernandez Mancera
2026-05-28 11:12 ` Stefano Brivio
2026-05-28 11:29 ` Fernando Fernandez Mancera
2026-05-28 12:29 ` Thorsten Leemhuis
2026-05-28 13:32 ` Stefano Brivio
2026-05-28 14:02 ` Thorsten Leemhuis
2026-05-28 14:15 ` Íñigo Huguet
2026-05-28 14:53 ` Stefano Brivio
2026-05-28 15:24 ` Íñigo Huguet
2026-05-28 16:01 ` Beniamino Galvani
2026-05-28 17:21 ` Stefano Brivio
2026-05-28 18:42 ` Fernando Fernandez Mancera
2026-05-28 18:50 ` Fernando Fernandez Mancera
2026-05-28 19:22 ` Stefano Brivio
2026-05-29 4:47 ` David Gibson
2026-05-29 8:40 ` Beniamino Galvani
2026-05-29 17:40 ` Stefano Brivio
2026-05-28 14:34 ` Andrew Lunn
2026-05-28 15:17 ` Stefano Brivio
2026-05-29 4:48 ` David Gibson
2026-05-29 9:42 ` Stefano Brivio
-- strict thread matches above, loose matches on Subject: below --
2026-05-29 18:28 Tj
2026-05-29 20:04 ` Stefano Brivio
2026-05-29 20:18 ` Tj
2026-06-01 8:08 ` Stefano Brivio
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=20260527211356.GA16443@cmadams.net \
--to=linux@cmadams$(echo .)net \
--cc=fmancera@suse$(echo .)de \
--cc=idosch@idosch$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--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