From: Dan Moulding <dan@danm.net>
To: bagasdotme@gmail.com
Cc: alexhenrie24@gmail.com, dan@danm.net, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com,
regressions@lists.linux.dev
Subject: Re: [REGRESSION] net/ipv6/addrconf: Temporary addresses with short lifetimes generating when they shouldn't, causing applications to fail
Date: Fri, 22 Dec 2023 08:37:03 -0700 [thread overview]
Message-ID: <20231222153703.11268-1-dan@danm.net> (raw)
In-Reply-To: <ZYWNr_4P-je2uVDe@archie.me>
> > I bisected it to commit 629df6701c8a ("net: ipv6/addrconf: clamp
> > preferred_lft to the minimum required"). Upon reviewing that change, I
> > see that it has changed when generation of temporary addresses will be
> > allowed. I believe that change might have inadvertently caused the
> > kernel to violate RFC 4941 and might need to be reverted.
>
> Can you verify that by actually reverting 629df6701c8a91 on top of net
> tree?
Yes, after bisecting it to that commit, I did revert it on top of
v6.7-rc6 and verified that the problem goes away. It doesn't start
accumulating addresses once every second. Instead the single temporary
address that was generated for the deprecated prefix is still there,
with a preferred lifetime of 0, like I'd expect, and no new addresses
get generated. The application-level problems are also gone (Chromium
loads pages without issue, and avahi-daemon hasn't jumped to 100%
CPU).
I'm now running it this way on several machines and everything is
looking good again.
-- Dan
next prev parent reply other threads:[~2023-12-22 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 23:10 [REGRESSION] net/ipv6/addrconf: Temporary addresses with short lifetimes generating when they shouldn't, causing applications to fail Dan Moulding
2023-12-22 13:22 ` Bagas Sanjaya
2023-12-22 15:37 ` Dan Moulding [this message]
2023-12-22 23:42 ` Alex Henrie
2023-12-22 23:42 ` [PATCH net] net: ipv6/addrconf: clamp temporary address's preferred lifetime to public address's Alex Henrie
2023-12-23 15:22 ` [REGRESSION] net/ipv6/addrconf: Temporary addresses with short lifetimes generating when they shouldn't, causing applications to fail Dan Moulding
2023-12-24 0:07 ` Alex Henrie
2023-12-29 16:33 ` Dan Moulding
2023-12-29 22:52 ` David Ahern
2023-12-30 4:12 ` Alex Henrie
2023-12-23 8:42 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=20231222153703.11268-1-dan@danm.net \
--to=dan@danm.net \
--cc=alexhenrie24@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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