From: Paolo Abeni <pabeni@redhat.com>
To: Yuyang Huang <sigefriedhyy@gmail.com>, netdev-bot+sashiko@kernel.org
Cc: ajay.kathat@microchip.com, aleksandr.loktionov@intel.com,
andrew+netdev@lunn.ch, claudiu.beznea@tuxon.dev,
davem@davemloft.net, dsahern@kernel.org, donald.hunter@gmail.com,
edumazet@google.com, idosch@nvidia.com, jacob.e.keller@intel.com,
kuba@kernel.org, johannes@sipsolutions.net, kees@kernel.org,
kory.maincent@bootlin.com, kuniyu@google.com,
nicolas.dichtel@6wind.com, nickgarlis@gmail.com,
sd@queasysnail.net, shuah@kernel.org, horms@kernel.org,
sdf.kernel@gmail.com, vadim.fedorenko@linux.dev,
willemb@google.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v11 3/6] net: add a generation counter for dev->mc changes
Date: Mon, 19 Oct 2026 13:19:13 +0200 [thread overview]
Message-ID: <8dcd9564-e9a3-4b00-93b8-3cb023d68047@redhat.com> (raw)
In-Reply-To: <CA+7S2v+LHUWXQMD-cYPEzT5-f3Qhw_vz+LEssQH_A_oqDKtnnA@mail.gmail.com>
On 10/13/26 12:25, Yuyang Huang wrote:
>> - [Low] The commit message misdescribes the precedent it copies.
>
> Looks like a nit, will adjust it if need new revision.
>
>> - [Low] The patch adds an 8-byte 'struct net_device *mc_dev' to every
>> struct netdev_hw_addr_list (include/linux/netdevice.h:253), but only…
>
> It seems to me this issue by itself doesn't deserve a revision. Will
> fix it if new revision is required.
I agree this is not a blocker, but I think it would be nice if you could
follow-up on this one.
The solution proposed by the LLM LGTM.
>
>> - [Low] __hw_addr_changed() (net/core/dev_addr_lists.c:22-26) reads the
>> device netns with plain dev_net(list->mc_dev).
>
> This was raised on earlier versions. Every dev->mc writer already
> reads dev_net() under only the address lock, so this adds no new race.
Same here.
Also, still speaking of possible follow-up, I think it would be nice if
you could change the addr list lifecycle to RCU (no idea of how much
complex would be that).
Thanks,
Paolo
next prev parent reply other threads:[~2026-10-19 11:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 1:17 [PATCH net-next v11 0/6] rtnetlink: dump link-layer multicast addresses Yuyang Huang
2026-10-12 1:17 ` [PATCH net-next v11 1/6] netlink: specs: rt-addr: fix the type of target-netnsid Yuyang Huang
2026-10-13 2:04 ` netdev-bot+sashiko
2026-10-13 10:21 ` Yuyang Huang
2026-10-12 1:17 ` [PATCH net-next v11 2/6] net: change netdev_hw_addr_list count through helpers Yuyang Huang
2026-10-12 1:17 ` [PATCH net-next v11 3/6] net: add a generation counter for dev->mc changes Yuyang Huang
2026-10-13 2:04 ` netdev-bot+sashiko
2026-10-13 10:25 ` Yuyang Huang
2026-10-19 11:19 ` Paolo Abeni [this message]
2026-10-19 11:35 ` Yuyang Huang
2026-10-12 1:17 ` [PATCH net-next v11 4/6] net: add AF_PACKET multicast dumps Yuyang Huang
2026-10-13 2:05 ` netdev-bot+sashiko
2026-10-13 10:27 ` Yuyang Huang
2026-10-12 1:17 ` [PATCH net-next v11 5/6] netlink: specs: rt-addr: document " Yuyang Huang
2026-10-12 1:17 ` [PATCH net-next v11 6/6] selftests: net: test " Yuyang Huang
2026-10-14 10:46 ` Loktionov, Aleksandr
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=8dcd9564-e9a3-4b00-93b8-3cb023d68047@redhat.com \
--to=pabeni@redhat.com \
--cc=ajay.kathat@microchip.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kees@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nickgarlis@gmail.com \
--cc=nicolas.dichtel@6wind.com \
--cc=sd@queasysnail.net \
--cc=sdf.kernel@gmail.com \
--cc=shuah@kernel.org \
--cc=sigefriedhyy@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=willemb@google.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®