From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Yuyang Huang <sigefriedhyy@gmail.com>
Cc: Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Ido Schimmel <idosch@nvidia.com>,
Jacob Keller <jacob.e.keller@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Nikolaos Gkarlis <nickgarlis@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Sabrina Dubroca <sd@queasysnail.net>,
Shuah Khan <shuah@kernel.org>, Simon Horman <horms@kernel.org>,
Stanislav Fomichev <sdf.kernel@gmail.com>,
Willem de Bruijn <willemb@google.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v7 2/5] net: add a generation counter for dev->mc changes
Date: Fri, 25 Sep 2026 10:17:31 +0200 [thread overview]
Message-ID: <6541b309-4e1f-462b-a867-57b67bba1b94@6wind.com> (raw)
In-Reply-To: <20260924011554.3494-3-sigefriedhyy@gmail.com>
Le 24/09/2026 à 03:15, Yuyang Huang a écrit :
> A multi-part RTM_GETMULTICAST dump of dev->mc resumes by position, so
> entries added or removed between two dump rounds can be skipped or
> repeated. The IPv4 and IPv6 dumps report that with NLM_F_DUMP_INTR by
> stamping cb->seq from a per netns generation counter combined with
> dev_base_seq, see inet_base_seq().
>
> Add the equivalent for the device multicast lists: a per netns counter
> bumped whenever an entry is added to or removed from any dev->mc. The
> list helpers do not know which device a list belongs to, so give
> netdev_hw_addr_list an owner set for dev->mc only and bump the counter
> of dev_net(owner) where entries are created and freed. That covers the
> dev_mc_* helpers, both lists of a sync, the hardware sync helpers
> drivers call from their rx mode callbacks or their own workers and the
> reconciliation after an asynchronous rx mode update, while snapshot
> and other lists have no owner and are not tracked. It is atomic since
> the writers only hold the address lock of their own device.
>
> Used by the following patch for the AF_PACKET multicast dump.
>
> Signed-off-by: Yuyang Huang <sigefriedhyy@gmail.com>
> ---
> include/linux/netdevice.h | 3 +++
> include/net/net_namespace.h | 1 +
> net/core/dev_addr_lists.c | 21 +++++++++++++++++++++
> 3 files changed, 25 insertions(+)
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 5d16737167ee..be3804cdbb2d 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -256,6 +256,9 @@ struct netdev_hw_addr_list {
>
> /* Auxiliary tree for faster lookup on addition and deletion */
> struct rb_root tree;
> +
> + /* Set for dev->mc, the owning device of a tracked list */
> + struct net_device *owner;
There are several lists owned by a device (dev->dev_addrs, dev->uc, dev->mc,
dev->rx_mode_addr_cache), the name 'owner' does not reflect that it is set only
when the list is dev->mc.
I wonder if the name should be changed or if __hw_addr_init() should be updated
to always set owner when the list is owned by a device.
> };
>
> #define netdev_hw_addr_list_count(l) ((l)->count)
> diff --git a/include/net/net_namespace.h b/include/net/net_namespace.h
> index 46b4c67e2966..d8c681ab5c74 100644
> --- a/include/net/net_namespace.h
> +++ b/include/net/net_namespace.h
> @@ -71,6 +71,7 @@ struct net {
> spinlock_t rules_mod_lock;
>
> unsigned int dev_base_seq; /* protected by rtnl_mutex */
> + atomic_t dev_mc_genid; /* bumped on dev->mc changes */
> u32 ifindex;
>
> spinlock_t nsid_lock;
> diff --git a/net/core/dev_addr_lists.c b/net/core/dev_addr_lists.c
> index 08528ca0a8b3..18acd874fdbd 100644
> --- a/net/core/dev_addr_lists.c
> +++ b/net/core/dev_addr_lists.c
> @@ -16,6 +16,19 @@
>
> #include "dev.h"
>
> +/**
> + * __hw_addr_changed - account a change of a tracked address list
> + * @list: the address list an entry was added to or removed from
> + *
> + * Bumps the netns generation counter RTM_GETMULTICAST dumps use to detect
> + * changes of dev->mc between dump rounds. Untracked lists have no owner.
> + */
> +static void __hw_addr_changed(struct netdev_hw_addr_list *list)
> +{
> + if (list->owner)
> + atomic_inc(&dev_net(list->owner)->dev_mc_genid);
> +}
> +
> /*
> * General list handling functions
> */
> @@ -126,6 +139,7 @@ static int __hw_addr_add_ex(struct netdev_hw_addr_list *list,
>
> list_add_tail_rcu(&ha->list, &list->list);
> list->count++;
> + __hw_addr_changed(list);
list->count and dev_mc_genid evolves together. Perhaps some helpers would be
less error-prone for future patches?
__hw_addr_count_inc()
__hw_addr_count_dec()
__hw_addr_count_reset()
?
>
> return 0;
> }
> @@ -162,6 +176,7 @@ static int __hw_addr_del_entry(struct netdev_hw_addr_list *list,
> list_del_rcu(&ha->list);
> kfree_rcu(ha, rcu_head);
> list->count--;
> + __hw_addr_changed(list);
> return 0;
> }
>
> @@ -487,6 +502,8 @@ void __hw_addr_flush(struct netdev_hw_addr_list *list)
> {
> struct netdev_hw_addr *ha, *tmp;
>
> + if (list->count)
> + __hw_addr_changed(list);
> list->tree = RB_ROOT;
> list_for_each_entry_safe(ha, tmp, &list->list, list) {
> list_del_rcu(&ha->list);
> @@ -501,6 +518,7 @@ void __hw_addr_init(struct netdev_hw_addr_list *list)
> INIT_LIST_HEAD(&list->list);
> list->count = 0;
> list->tree = RB_ROOT;
> + list->owner = NULL;
> }
> EXPORT_SYMBOL(__hw_addr_init);
>
> @@ -612,6 +630,7 @@ void __hw_addr_list_reconcile(struct netdev_hw_addr_list *real_list,
> __hw_addr_insert(real_list, ref_ha,
> addr_len);
> real_list->count++;
> + __hw_addr_changed(real_list);
> }
> continue;
> }
> @@ -623,6 +642,7 @@ void __hw_addr_list_reconcile(struct netdev_hw_addr_list *real_list,
> list_del_rcu(&real_ha->list);
> kfree_rcu(real_ha, rcu_head);
> real_list->count--;
> + __hw_addr_changed(real_list);
> }
> }
>
> @@ -1177,6 +1197,7 @@ EXPORT_SYMBOL(dev_mc_flush);
> void dev_mc_init(struct net_device *dev)
> {
> __hw_addr_init(&dev->mc);
> + dev->mc.owner = dev;
> }
> EXPORT_SYMBOL(dev_mc_init);
>
next prev parent reply other threads:[~2026-09-25 8:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 1:15 [PATCH net-next v7 0/5] rtnetlink: dump link-layer multicast addresses Yuyang Huang
2026-09-24 1:15 ` [PATCH net-next v7 1/5] netlink: specs: rt-addr: fix the type of target-netnsid Yuyang Huang
2026-09-24 1:15 ` [PATCH net-next v7 2/5] net: add a generation counter for dev->mc changes Yuyang Huang
2026-09-25 7:58 ` Nicolas Dichtel
2026-09-25 8:06 ` Nicolas Dichtel
2026-09-25 8:17 ` Nicolas Dichtel [this message]
2026-09-24 1:15 ` [PATCH net-next v7 3/5] net: add AF_PACKET multicast dumps Yuyang Huang
2026-09-25 8:29 ` Nicolas Dichtel
2026-09-24 1:15 ` [PATCH net-next v7 4/5] netlink: specs: rt-addr: document " Yuyang Huang
2026-09-24 1:15 ` [PATCH net-next v7 5/5] selftests: net: test " Yuyang Huang
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=6541b309-4e1f-462b-a867-57b67bba1b94@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=aleksandr.loktionov@intel.com \
--cc=andrew+netdev@lunn.ch \
--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=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nickgarlis@gmail.com \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=sdf.kernel@gmail.com \
--cc=shuah@kernel.org \
--cc=sigefriedhyy@gmail.com \
--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®