From: Jakub Kicinski <kuba@kernel.org>
To: Daehyeon Ko <4ncienth@gmail.com>
Cc: David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@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 0/2] ipv6: fix address publication races with addrconf_ifdown
Date: Mon, 5 Oct 2026 17:17:29 -0700 [thread overview]
Message-ID: <20261005171729.65fda9d6@kernel.org> (raw)
In-Reply-To: <20261005165706.6ca89a76@kernel.org>
On Mon, 5 Oct 2026 16:57:06 -0700 Jakub Kicinski wrote:
> On Mon, 5 Oct 2026 03:36:37 +0900 Daehyeon Ko wrote:
> > The first patch serializes address publication with device teardown by
> > taking idev->lock before the address hash lock, as suggested by Ido. It
> > rechecks both dead and disable_ipv6 before publishing.
>
> Please slow down. We don't want to see more than 10 outstanding patches
> from random "LLM people" in the review queue. Please look at your
> outstanding patches here:
> https://patchwork.kernel.org/project/netdevbpf/list/?submitter=223024
Herm, you seem to also have a tendency to make minor adjustments
to the subject. Please try to avoid that unless really necessary.
It breaks the quite naive version tracking kernel.org infra does
for us.
prev parent reply other threads:[~2026-10-06 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 18:36 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-04 18:36 ` [PATCH net v2 2/2] ipv6: remove ifaddr from hash during ifdown list cleanup Daehyeon Ko
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 [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=20261005171729.65fda9d6@kernel.org \
--to=kuba@kernel.org \
--cc=4ncienth@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--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
all inboxes | Powered by JetHome®