From: Daehyeon Ko <4ncienth@gmail.com>
To: Ido Schimmel <idosch@nvidia.com>
Cc: Daehyeon Ko <4ncienth@gmail.com>,
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 v3 1/3] ipv6: serialize address publication with device teardown
Date: Thu, 15 Oct 2026 14:05:51 +0900 [thread overview]
Message-ID: <20261015050553.1835517-1-4ncienth@gmail.com> (raw)
In-Reply-To: <20261012145306.GB779501@shredder>
You are right. I overlooked both earlier comments. V4 drops the preliminary
READ_ONCE() conversions and the disable_ipv6 recheck. The new locking now
serializes only idev->dead, the state relevant to the reference leak, and
leaves the existing preliminary checks unchanged. Sorry for the churn.
next prev parent reply other threads:[~2026-10-15 5:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 5:40 [PATCH net v3 0/3] ipv6: fix address publication races with addrconf_ifdown Daehyeon Ko
2026-10-09 5:40 ` [PATCH net v3 1/3] ipv6: serialize address publication with device teardown Daehyeon Ko
2026-10-10 5:43 ` netdev-bot+sashiko
2026-10-12 15:13 ` Ido Schimmel
2026-10-15 5:06 ` Daehyeon Ko
2026-10-12 14:53 ` Ido Schimmel
2026-10-15 5:05 ` Daehyeon Ko [this message]
2026-10-09 5:40 ` [PATCH net v3 2/3] ipv6: remove ifaddr from hash during ifdown list cleanup Daehyeon Ko
2026-10-10 5:43 ` netdev-bot+sashiko
2026-10-09 5:40 ` [PATCH net v3 3/3] ipv6: initialize temporary ifaddr before publication Daehyeon Ko
2026-10-10 5:43 ` netdev-bot+sashiko
2026-10-12 14:52 ` Ido Schimmel
2026-10-09 5:44 ` [PATCH net v3 0/3] ipv6: fix address publication races with addrconf_ifdown netdev-bot+sinfo
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=20261015050553.1835517-1-4ncienth@gmail.com \
--to=4ncienth@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox