From: Simon Horman <horms@kernel.org>
To: xiaoliang.yang_1@nxp.com
Cc: Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
jhs@mojatatu.com, jiri@resnulli.us, shuah@kernel.org,
vladimir.oltean@nxp.com, vinicius.gomes@intel.com,
fejes@inf.elte.hu
Subject: Re: [PATCH net-next 5/6] selftest: add tc-testing JSON test cases for act_frer
Date: Fri, 24 Jul 2026 13:34:13 +0100 [thread overview]
Message-ID: <20260724123413.670856-1-horms@kernel.org> (raw)
In-Reply-To: <20260717095549.10565-6-xiaoliang.yang_1@nxp.com>
This is an AI-generated review of your patch. The human sending this
email has considered the AI review valid, or at least plausible.
Full review at: https://sashiko.dev/#/patchset/20260717095549.10565-3-xiaoliang.yang_1@nxp.com?part=5
---
--- Patch [5]: [PATCH net-next 5/6] selftest: add tc-testing JSON test cases for act_frer ---
commit a49cd24c7418264cc3093ec982fc3e60a41c9d2b
Author: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
selftest: add tc-testing JSON test cases for act_frer
This commit adds a tc-testing JSON file covering the FRER (IEEE 802.1CB
Frame Replication and Elimination for Reliability) tc action. It introduces
32 test cases that exercise various parameters, statistics, and filter
bindings.
> diff --git a/tools/testing/selftests/tc-testing/tc-tests/actions/frer.json b/tools/testing/selftests/tc-testing/tc-tests/actions/frer.json
> new file mode 100644
> index 0000000000000..d5be6ae156f79
> --- /dev/null
> +++ b/tools/testing/selftests/tc-testing/tc-tests/actions/frer.json
> @@ -0,0 +1,785 @@
> +[
[ ... ]
> + {
> + "id": "frer_0027",
> + "name": "Bind frer push action to egress clsact filter",
> + "category": [
> + "actions",
> + "frer"
> + ],
> + "setup": [
> + [
> + "modprobe act_frer",
> + 0,
> + 1
> + ],
> + "ip link del frer_dummy 2>/dev/null || true",
> + "ip link add frer_dummy type dummy",
> + "ip link set frer_dummy up",
[Severity: Medium]
Will these tests run in the host's default network namespace because they omit
the nsPlugin requirement?
If a test aborts or crashes before the teardown stage, this could leak dummy
interfaces into the host's root namespace.
[ ... ]
> + {
> + "id": "frer_0029",
> + "name": "Share frer recover action across two ingress filters (refcount check)",
> + "category": [
> + "actions",
> + "frer"
> + ],
> + "setup": [
> + [
> + "modprobe act_frer",
> + 0,
> + 1
> + ],
> + "ip link del frer_a 2>/dev/null || true",
> + "ip link del frer_b 2>/dev/null || true",
> + "ip link add frer_a type dummy",
> + "ip link add frer_b type dummy",
[Severity: Medium]
Similarly, will these dummy interfaces also leak into the host network
namespace if the test fails before teardown?
Could these tests be updated to require nsPlugin to ensure they run in an
isolated network namespace?
next prev parent reply other threads:[~2026-07-24 12:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 9:55 [PATCH net-next 0/6] tc: introduce FRER action (IEEE 802.1CB) Xiaoliang Yang
2026-07-17 9:55 ` [PATCH net-next 1/6] uapi: if_ether: add ETH_P_RTAG for IEEE 802.1CB R-TAG Xiaoliang Yang
2026-07-17 9:55 ` [PATCH net-next 2/6] uapi: pkt_cls: add TCA_ID_FRER action identifier Xiaoliang Yang
2026-07-17 9:55 ` [PATCH net-next 3/6] uapi: tc_act: add tc_frer UAPI header Xiaoliang Yang
2026-07-24 11:49 ` Simon Horman
2026-07-17 9:55 ` [PATCH net-next 4/6] net: sched: act_frer: add FRER tc action Xiaoliang Yang
2026-07-24 12:33 ` Simon Horman
2026-07-17 9:55 ` [PATCH net-next 5/6] selftest: add tc-testing JSON test cases for act_frer Xiaoliang Yang
2026-07-24 12:34 ` Simon Horman [this message]
2026-07-17 9:55 ` [PATCH net-next 6/6] selftests: net: add kselftest for IEEE 802.1CB FRER tc action Xiaoliang Yang
2026-07-24 12:48 ` Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2026-06-22 9:21 [PATCH net-next 0/6] tc: introduce FRER action (IEEE 802.1CB) Xiaoliang Yang
2026-06-22 9:21 ` [PATCH net-next 5/6] selftest: add tc-testing JSON test cases for act_frer Xiaoliang Yang
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=20260724123413.670856-1-horms@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fejes@inf.elte.hu \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@nxp.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