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 3/5] net: add AF_PACKET multicast dumps
Date: Fri, 25 Sep 2026 10:29:30 +0200 [thread overview]
Message-ID: <361c4480-0a3b-476f-9f93-a07cf4d5eef7@6wind.com> (raw)
In-Reply-To: <20260924011554.3494-4-sigefriedhyy@gmail.com>
Le 24/09/2026 à 03:15, Yuyang Huang a écrit :
> RTM_GETMULTICAST dumps IPv4 and IPv6 multicast group memberships, but
> the device multicast list (dev->mc) is only available through
> /proc/net/dev_mcast, so "ip maddr show" still has to parse procfs for
> its link-layer entries.
>
> Handle RTM_GETMULTICAST dumps with ifa_family set to AF_PACKET next to
> the dev->mc helpers in dev_addr_lists.c and report every entry of
> dev->mc in the existing ifaddrmsg format:
>
> - IFA_MULTICAST carries the raw link-layer address
> - IFA_MC_USERS carries the entry reference count
> - IFA_F_GLOBAL in IFA_FLAGS reports netdev_hw_addr::global_use, set
> by dev_mc_add_global() (SIOCADDMULTI) and dev_mc_add_excl()
> ("bridge fdb add ... self"), i.e. entries added explicitly rather
> than by a protocol join. This is the static column of
> /proc/net/dev_mcast
> - ifa_scope is RT_SCOPE_LINK
>
> This covers every column of /proc/net/dev_mcast. AF_PACKET is the
> family iproute2 already uses for link-layer addresses ("ip -0").
>
> The default FDB dump also walks dev->mc, but only for Ethernet devices
> without an ndo_fdb_dump of their own, so bridge, vxlan or macvlan
> devices never show their multicast filter there, and it has no users
> count or global_use bit. Extending it would change "bridge fdb show"
> output and add NDA_* attributes.
>
> Requests are always validated, there are no legacy users: prefixlen,
> flags and scope must be zero, ifa_index selects one device and
> IFA_TARGET_NETNSID is the only attribute accepted. The dump runs under
> RCU and netif_addr_lock_bh() without RTNL. cb->seq is sampled from the
> dev->mc generation counter and dev_base_seq under the address lock of
> each device and again when a round ends, so a change since the previous
> device or dump round sets NLM_F_DUMP_INTR, also when the last round
> dumps nothing because the device it stopped at is gone.
>
> Signed-off-by: Yuyang Huang <sigefriedhyy@gmail.com>
Reviewed-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
next prev parent reply other threads:[~2026-09-25 8:29 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
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 [this message]
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=361c4480-0a3b-476f-9f93-a07cf4d5eef7@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®