From: Paolo Abeni <pabeni@redhat.com>
To: Linmao Li <lilinmao@kylinos.cn>,
davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org
Cc: horms@kernel.org, stephen@networkplumber.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] ipv6: addrconf: skip ERRDAD transition when address already DEAD
Date: Tue, 28 Apr 2026 12:59:21 +0200 [thread overview]
Message-ID: <d7bab1a1-6938-49aa-9fdb-fab42633c678@redhat.com> (raw)
In-Reply-To: <20260423023216.1221731-1-lilinmao@kylinos.cn>
On 4/23/26 4:32 AM, Linmao Li wrote:
> addrconf_dad_failure() transitions ifp->state from DAD to POSTDAD
> via addrconf_dad_end(), which drops ifp->lock on return. The lock
> is re-acquired after net_info_ratelimited(). A concurrent
> ipv6_del_addr() can take the lock in that window, set ifp->state
> to DEAD and run list_del_rcu(&ifp->if_list).
>
> addrconf_dad_failure() then overwrites DEAD with ERRDAD at errdad:
> and schedules a new dad_work. The work calls ipv6_del_addr()
> again, hitting the already-poisoned list entry:
>
> general protection fault: 0000 [#1] SMP NOPTI
> CPU: 4 PID: 217 Comm: kworker/4:1
> Workqueue: ipv6_addrconf addrconf_dad_work
> RIP: 0010:ipv6_del_addr+0xe9/0x280
> RAX: dead000000000122
> Call Trace:
> addrconf_dad_stop+0x113/0x140
> addrconf_dad_work+0x28c/0x430
> process_one_work+0x1eb/0x3b0
> worker_thread+0x4d/0x400
> kthread+0x104/0x140
> ret_from_fork+0x35/0x40
>
> Fold the addrconf_dad_end() logic into addrconf_dad_failure()
> under a single ifp->lock critical section. The STABLE_PRIVACY
> branch temporarily drops ifp->lock, so keep a state-is-DEAD
> bail-out at errdad: for that remaining window.
>
> Fixes: c15b1ccadb32 ("ipv6: move DAD and addrconf_verify processing to workqueue")
> Signed-off-by: Linmao Li <lilinmao@kylinos.cn>
> ---
> net/ipv6/addrconf.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c
> index 5476b6536eb7..c9ea0d5042d0 100644
> --- a/net/ipv6/addrconf.c
> +++ b/net/ipv6/addrconf.c
> @@ -2166,16 +2166,18 @@ void addrconf_dad_failure(struct sk_buff *skb, struct inet6_ifaddr *ifp)
> struct net *net = dev_net(idev->dev);
> int max_addresses;
>
> - if (addrconf_dad_end(ifp)) {
> + spin_lock_bh(&ifp->lock);
> +
> + if (ifp->state != INET6_IFADDR_STATE_DAD) {
> + spin_unlock_bh(&ifp->lock);
> in6_ifa_put(ifp);
> return;
> }
> + ifp->state = INET6_IFADDR_STATE_POSTDAD;
>
> net_info_ratelimited("%s: IPv6 duplicate address %pI6c used by %pM detected!\n",
> ifp->idev->dev->name, &ifp->addr, eth_hdr(skb)->h_source);
>
> - spin_lock_bh(&ifp->lock);
> -
> if (ifp->flags & IFA_F_STABLE_PRIVACY) {
> struct in6_addr new_addr;
> struct inet6_ifaddr *ifp2;
> @@ -2227,6 +2229,11 @@ void addrconf_dad_failure(struct sk_buff *skb, struct inet6_ifaddr *ifp)
>
> errdad:
> /* transition from _POSTDAD to _ERRDAD */
> + if (ifp->state == INET6_IFADDR_STATE_DEAD) {
> + spin_unlock_bh(&ifp->lock);
> + in6_ifa_put(ifp);
> + return;
It looks like this check is need only when the ifp->lock is released
again, i.e. just after the `lock_errdad`. Please move it there, to avoid
confusion when looking at this code in the future.
Thanks,
Paolo
next prev parent reply other threads:[~2026-04-28 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 3:28 [PATCH net] ipv6: addrconf: skip ERRDAD transition when address already DEAD Linmao Li
2026-04-21 7:50 ` [PATCH net v2] " Linmao Li
2026-04-22 10:43 ` Sabrina Dubroca
2026-04-23 2:32 ` [PATCH net v3] " Linmao Li
2026-04-28 10:59 ` Paolo Abeni [this message]
2026-04-29 1:26 ` [PATCH net v4] " Linmao Li
2026-04-29 9:08 ` Ido Schimmel
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=d7bab1a1-6938-49aa-9fdb-fab42633c678@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lilinmao@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox