From: Simon Horman <horms@kernel.org>
To: Eric Woudstra <ericwouds@gmail.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Nikolay Aleksandrov <razor@blackwall.org>,
Vladimir Oltean <olteanv@gmail.com>,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [RFC PATCH v2 nf-next] selftests: netfilter: Add bridge_fastpath.sh
Date: Tue, 17 Jun 2025 12:34:14 +0100 [thread overview]
Message-ID: <20250617113414.GI5000@horms.kernel.org> (raw)
In-Reply-To: <20250617065930.23647-1-ericwouds@gmail.com>
On Tue, Jun 17, 2025 at 08:59:30AM +0200, Eric Woudstra wrote:
> Add a script to test various scenarios where a bridge is involved
> in the fastpath. It runs tests in the forward path, and also in
> a bridged path.
>
> The setup is similar to a basic home router with multiple lan ports.
>
> It uses 3 pairs of veth-devices. Each or all pairs can be
> replaced by a pair of real interfaces, interconnected by wire.
> This is necessary to test the behavior when dealing with
> dsa ports, foreign (dsa) ports and switchdev userports that support
> SWITCHDEV_OBJ_ID_PORT_VLAN.
>
> See the head of the script for a detailed description.
>
> Run without arguments to perform all tests on veth-devices.
>
> Signed-off-by: Eric Woudstra <ericwouds@gmail.com>
Hi Eric,
If this proposal proceeds could you please consider running shellcheck over
the script and address the warnings it flags produces.
A shellcheck test was recently added to NIPA and we'd like to at least
minimise adding new warnings to the tree.
next prev parent reply other threads:[~2025-06-17 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 6:59 [RFC PATCH v2 nf-next] selftests: netfilter: Add bridge_fastpath.sh Eric Woudstra
2025-06-17 11:34 ` Simon Horman [this message]
2025-06-23 13:14 ` Florian Westphal
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=20250617113414.GI5000@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericwouds@gmail.com \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--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.