From: Ido Schimmel <idosch@nvidia.com>
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: David Ahern <dsahern@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 1/2] ipv6: serialize address publication with device teardown
Date: Wed, 7 Oct 2026 19:46:09 +0300 [thread overview]
Message-ID: <20261007164609.GB1153540@shredder> (raw)
In-Reply-To: <20261004183639.3773498-2-4ncienth@gmail.com>
On Mon, Oct 05, 2026 at 03:36:38AM +0900, Daehyeon Ko wrote:
> ipv6_add_addr() checks idev state before allocating an ifaddr, but
> publishes the object later. addrconf_ifdown() can mark and detach the
> idev between the check and publication.
>
> This happens when a non-loopback device MTU falls below IPV6_MIN_MTU. A
> forced interleaving published an address on a dead idev, and later device
> deletion waited indefinitely for the leaked references.
>
> Protect the dead indication with idev->lock and keep that lock across
> both hash and device-list publication. Recheck both dead and
> disable_ipv6 before publishing. If teardown wins, reject the unpublished
> object.
>
> Fixes: 8814c4b53381 ("[IPV6] ADDRCONF: Convert addrconf_lock to RCU.")
> Cc: stable@vger.kernel.org
> Suggested-by: Ido Schimmel <idosch@nvidia.com>
> Assisted-by: LLM
> Signed-off-by: Daehyeon Ko <4ncienth@gmail.com>
> ---
> net/ipv6/addrconf.c | 14 +++++++++++---
> 1 file changed, 11 insertions(+), 3 deletions(-)
>
> diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
> index c90ee6dd7446cd..426739abb07440 100644
> --- a/net/ipv6/addrconf.c
> +++ b/net/ipv6/addrconf.c
> @@ -1168,14 +1168,20 @@ ipv6_add_addr(struct inet6_dev *idev, struct ifa6_config *cfg,
>
> rcu_read_lock();
>
> - err = ipv6_add_addr_hash(idev->dev, ifa);
> + write_lock_bh(&idev->lock);
> +
> + if (idev->dead)
> + err = -ENODEV;
> + else if (READ_ONCE(idev->cnf.disable_ipv6))
> + err = -EACCES;
Why do you need this check? 'disable_ipv6' is not set under the idev
lock and it's checked earlier in the function. The fix here is strictly
about adding an address on a dead idev, as such an address will not be
cleaned up and keep holding a reference on the idev which in turn holds
a reference on the net device.
> + else
> + err = ipv6_add_addr_hash(idev->dev, ifa);
> if (err < 0) {
> + write_unlock_bh(&idev->lock);
> rcu_read_unlock();
> goto out;
> }
>
> - write_lock_bh(&idev->lock);
> -
> /* Add to inet6_dev unicast addr list. */
> ipv6_link_dev_addr(idev, ifa);
>
> @@ -3897,7 +3903,9 @@ static int addrconf_ifdown(struct net_device *dev, bool unregister)
> * Do not dev_put!
> */
> if (unregister) {
> + write_lock_bh(&idev->lock);
> WRITE_ONCE(idev->dead, 1);
> + write_unlock_bh(&idev->lock);
>
> /* protected by rtnl_lock */
> RCU_INIT_POINTER(dev->ip6_ptr, NULL);
> --
> 2.55.0
>
next prev parent reply other threads:[~2026-10-07 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 18:36 [PATCH net v2 0/2] ipv6: fix address publication races with addrconf_ifdown Daehyeon Ko
2026-10-04 18:36 ` [PATCH net v2 1/2] ipv6: serialize address publication with device teardown Daehyeon Ko
2026-10-05 18:39 ` netdev-bot+sashiko
2026-10-07 16:45 ` Ido Schimmel
2026-10-07 19:20 ` Ido Schimmel
2026-10-09 5:39 ` Daehyeon Ko
2026-10-07 16:46 ` Ido Schimmel [this message]
2026-10-04 18:36 ` [PATCH net v2 2/2] ipv6: remove ifaddr from hash during ifdown list cleanup Daehyeon Ko
2026-10-07 16:46 ` Ido Schimmel
2026-10-05 23:57 ` [PATCH net v2 0/2] ipv6: fix address publication races with addrconf_ifdown Jakub Kicinski
2026-10-06 0:17 ` Jakub Kicinski
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=20261007164609.GB1153540@shredder \
--to=idosch@nvidia.com \
--cc=4ncienth@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@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 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.