From: Jakub Kicinski <kuba@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: patchwork-bot+netdevbpf@kernel.org, netdev@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, fgont@si6networks.com
Subject: Re: [PATCH net v2] ipv6: addrconf: reduce default temp_valid_lft to 2 days
Date: Fri, 20 Feb 2026 12:28:04 -0800 [thread overview]
Message-ID: <20260220122804.572e70de@kernel.org> (raw)
In-Reply-To: <b3466d97-cbd2-4288-8da4-9f30df1ae477@suse.de>
On Fri, 20 Feb 2026 16:39:27 +0100 Fernando Fernandez Mancera wrote:
> > Here is the summary with links:
> > - [net,v2] ipv6: addrconf: reduce default temp_valid_lft to 2 days
> > https://git.kernel.org/netdev/net/c/9e371b0ba7f5
> >
>
> FTR; the patch was merged without the fixes tag. I think it would be
> good to backport this to stable kernels because otherwise the
> documentation and the real configured value are contradicting each other.
Yes, because it's a functional change. We can take it in for 7.0
but IMO the justification is too weak to treat it as a stable fix.
Imagine this from the perspective of someone who was promised
a _stable_ long term support kernel. If this change breaks their
expectations - what will be our defense? "But we said in the doc
(that nobody reads) that it was supposed to be 2 days"? Dunno.
Deciding backports is quite tricky, borderline impossible.
I took the executive decision to take the patch ASAP but not to stable.
Of course the stable auto-selection process may suck this patch in,
anyway. But I won't be culpable :)
prev parent reply other threads:[~2026-02-20 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 17:25 [PATCH net v2] ipv6: addrconf: reduce default temp_valid_lft to 2 days Fernando Fernandez Mancera
2026-02-15 9:34 ` Eric Dumazet
2026-02-18 1:20 ` patchwork-bot+netdevbpf
2026-02-20 15:39 ` Fernando Fernandez Mancera
2026-02-20 20:28 ` Jakub Kicinski [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=20260220122804.572e70de@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fgont@si6networks.com \
--cc=fmancera@suse.de \
--cc=horms@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.