From: Jakub Kicinski <kuba@kernel.org>
To: Hermin Anggawijaya <hermin.anggawijaya@alliedtelesis.co.nz>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] ipv6: addrconf: keep lifetimes of manual addresses on RA
Date: Fri, 30 Oct 2026 15:36:14 -0700 [thread overview]
Message-ID: <20261030153614.60de73d3@kernel.org> (raw)
In-Reply-To: <20261030055757.2094944-1-hermin.anggawijaya@alliedtelesis.co.nz>
On Fri, 30 Oct 2026 18:57:55 +1300 Hermin Anggawijaya wrote:
> A PIO with the autonomous flag set refreshes the lifetimes of any
> address on the interface that equals the address SLAAC would form from
> the prefix, including manually added ones. RFC 4862 Section 5.5.3 e)
> only applies this to addresses configured by stateless
> autoconfiguration, and the result is that a static, permanent address
> silently becomes one that expires.
## Form letter - net-next-closed
The merge window for Linux v7.4 has begun, and the net-next
tree is now closed for new drivers, features, code refactoring
and optimizations. We are currently accepting bug fixes only.
Please repost when net-next reopens. There is some uncertainty
about how long this merge window will last, so please check
https://netdev.bots.linux.dev/net-next.html
before reposting. net-next _may_ reopen on Nov 2nd.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: defer
pv-bot: closed
prev parent reply other threads:[~2026-10-30 22:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 5:57 [PATCH net-next 0/2] ipv6: addrconf: keep lifetimes of manual addresses on RA Hermin Anggawijaya
2026-10-30 5:57 ` [PATCH net-next 1/2] ipv6: addrconf: don't update lifetimes of manual addresses from RA Hermin Anggawijaya
2026-10-30 5:57 ` [PATCH net-next 2/2] selftests: net: test RA PIO handling of manually added addresses Hermin Anggawijaya
2026-10-30 22:36 ` 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=20261030153614.60de73d3@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=hermin.anggawijaya@alliedtelesis.co.nz \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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