From: Simon Horman <horms@kernel.org>
To: Yuyang Huang <yuyanghuang@google.com>
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"David Ahern" <dsahern@kernel.org>,
netdev@vger.kernel.org, "Donald Hunter" <donald.hunter@gmail.com>,
"Shuah Khan" <shuah@kernel.org>,
"Nikolay Aleksandrov" <razor@blackwall.org>,
"Hangbin Liu" <liuhangbin@gmail.com>,
"Daniel Borkmann" <daniel@iogearbox.net>,
petrm@nvidia.com, linux-kselftest@vger.kernel.org,
"Maciej Żenczykowski" <maze@google.com>,
"Lorenzo Colitti" <lorenzo@google.com>
Subject: Re: [PATCH net-next, v8 2/2] selftests/net: Add selftest for IPv4 RTM_GETMULTICAST support
Date: Mon, 10 Feb 2025 16:13:06 +0000 [thread overview]
Message-ID: <20250210161306.GE554665@kernel.org> (raw)
In-Reply-To: <20250207110836.2407224-2-yuyanghuang@google.com>
On Fri, Feb 07, 2025 at 08:08:36PM +0900, Yuyang Huang wrote:
> This change introduces a new selftest case to verify the functionality
> of dumping IPv4 multicast addresses using the RTM_GETMULTICAST netlink
> message. The test utilizes the ynl library to interact with the
> netlink interface and validate that the kernel correctly reports the
> joined IPv4 multicast addresses.
>
> To run the test, execute the following command:
>
> $ vng -v --user root --cpus 16 -- \
> make -C tools/testing/selftests TARGETS=net \
> TEST_PROGS=rtnetlink.py TEST_GEN_PROGS="" run_tests
>
> Cc: Maciej Żenczykowski <maze@google.com>
> Cc: Lorenzo Colitti <lorenzo@google.com>
> Signed-off-by: Yuyang Huang <yuyanghuang@google.com>
> ---
>
> Changelog since v7:
> - Create a new RtnlAddrFamily to load rt_addr.yaml.
>
> Changelog since v6:
> - Move `getmaddrs` definition to rt_addr.yaml.
>
> Documentation/netlink/specs/rt_addr.yaml | 23 ++++++++++++++
Hi Yuyang Huang,
FWIIW I think that the YAML spec entry is distinct from, although a
dependency of, adding the test. I would put it in a separate patch.
> tools/testing/selftests/net/Makefile | 1 +
> .../testing/selftests/net/lib/py/__init__.py | 2 +-
> tools/testing/selftests/net/lib/py/ynl.py | 4 +++
> tools/testing/selftests/net/rtnetlink.py | 30 +++++++++++++++++++
> 5 files changed, 59 insertions(+), 1 deletion(-)
> create mode 100755 tools/testing/selftests/net/rtnetlink.py
...
next prev parent reply other threads:[~2025-02-10 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 11:08 [PATCH net-next, v8 1/2] netlink: support dumping IPv4 multicast addresses Yuyang Huang
2025-02-07 11:08 ` [PATCH net-next, v8 2/2] selftests/net: Add selftest for IPv4 RTM_GETMULTICAST support Yuyang Huang
2025-02-10 16:13 ` Simon Horman [this message]
2025-02-11 5:43 ` Yuyang Huang
2025-02-11 10:05 ` Simon Horman
2025-02-11 10:40 ` [PATCH net-next, v8 1/2] netlink: support dumping IPv4 multicast addresses patchwork-bot+netdevbpf
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=20250210161306.GE554665@kernel.org \
--to=horms@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=shuah@kernel.org \
--cc=yuyanghuang@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;
as well as URLs for NNTP newsgroup(s).