From: Jakub Kicinski <kuba@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>
Cc: Petr Machata <petrm@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, David Ahern <dsahern@gmail.com>,
netdev@vger.kernel.org, Simon Horman <horms@kernel.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Ido Schimmel <idosch@nvidia.com>,
mlxsw@nvidia.com, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2 14/14] selftests: forwarding: Add a test for verifying VXLAN MC underlay
Date: Mon, 16 Jun 2025 10:52:59 -0700 [thread overview]
Message-ID: <20250616105259.2f09ce96@kernel.org> (raw)
In-Reply-To: <426a2c83-38ca-4fa2-9270-b3e600e30d19@kernel.org>
On Mon, 16 Jun 2025 18:18:18 +0200 Matthieu Baerts wrote:
> > The ALL_TESTS issue is not the end of it either. We use helpers that
> > call stuff indirectly all over the place. defer, in_ns... It would make
> > sense to me to just disable SC2317 in NIPA runs. Or maybe even put it in
> > net/forwarding/.shellcheckrc. Pretty much all those tests are written in
> > a style that will hit these issues.
>
> In this case, I think it would be better to add this .shellcheckrc file
> in net/forwarding. If you modify NIPA, I don't think people will know
> what is allowed or not, or what command line to use, no?
Let's do both? I disabled it to NIPA over the weekend.
next prev parent reply other threads:[~2025-06-16 17:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 20:10 [PATCH net-next v2 00/14] ipmr, ip6mr: Allow MC-routing locally-generated MC packets Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 01/14] net: ipv4: Add a flags argument to iptunnel_xmit(), udp_tunnel_xmit_skb() Petr Machata
2025-06-13 16:48 ` Jakub Kicinski
2025-06-13 19:23 ` Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 02/14] net: ipv4: ipmr: ipmr_queue_xmit(): Drop local variable `dev' Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 03/14] net: ipv4: ipmr: Split ipmr_queue_xmit() in two Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 04/14] net: ipv4: Add ip_mr_output() Petr Machata
2025-06-13 16:51 ` Jakub Kicinski
2025-06-13 19:31 ` Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 05/14] net: ipv6: Make udp_tunnel6_xmit_skb() void Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 06/14] net: ipv6: Add a flags argument to ip6tunnel_xmit(), udp_tunnel6_xmit_skb() Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 07/14] net: ipv6: ip6mr: Fix in/out netdev to pass to the FORWARD chain Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 08/14] net: ipv6: ip6mr: Extract a helper out of ip6mr_forward2() Petr Machata
2025-06-13 16:53 ` Jakub Kicinski
2025-06-13 19:40 ` Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 09/14] net: ipv6: Add ip6_mr_output() Petr Machata
2025-06-13 16:48 ` Jakub Kicinski
2025-06-13 18:59 ` Petr Machata
2025-06-13 21:52 ` Jakub Kicinski
2025-06-12 20:10 ` [PATCH net-next v2 10/14] vxlan: Support MC routing in the underlay Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 11/14] selftests: forwarding: lib: Move smcrouted helpers here Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 12/14] selftests: net: lib: Add ip_link_has_flag() Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 13/14] selftests: forwarding: adf_mcd_start(): Allow configuring custom interfaces Petr Machata
2025-06-12 20:10 ` [PATCH net-next v2 14/14] selftests: forwarding: Add a test for verifying VXLAN MC underlay Petr Machata
2025-06-13 16:57 ` Jakub Kicinski
2025-06-13 17:28 ` Matthieu Baerts
2025-06-16 15:06 ` Petr Machata
2025-06-16 16:18 ` Matthieu Baerts
2025-06-16 17:52 ` Jakub Kicinski [this message]
2025-06-16 19:53 ` Petr Machata
2025-06-16 20:40 ` Matthieu Baerts
2025-06-16 20:55 ` Jakub Kicinski
2025-06-13 15:48 ` [PATCH net-next v2 00/14] ipmr, ip6mr: Allow MC-routing locally-generated MC packets Jakub Kicinski
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=20250616105259.2f09ce96@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=shuah@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.