Re: [PATCH net v3 1/2] selftests: net: veth: propagate channel-check failures to exit status

From: netdev-bot+sashiko

Date: Wed Nov 18 2026 - 19:40:42 EST


Thank you for your contribution! Sashiko AI review found 1 potential
issue(s) to consider.

Critical: 0 · High: 0 · Medium: 1 · Low: 0

If you believe none of the issues are legitimate, please reply to each
issue of Medium severity or higher and explain why the AI is wrong.
If any of them are legitimate and you plan to respin, please let patchwork
know by including "pw-bot: cr" as a separate line at the end of your reply
(one such reply per series is enough).

- [Medium] The patch adds `ret=1` to the mismatch branch of
chk_channels() in tools/testing/selftests/net/veth.sh (line 133).

--

selftests: net: veth: propagate channel-check failures to exit status

This commit makes chk_channels() in veth.sh set ret=1 when the observed
channel counts do not match the expected ones. With it, any channel
mismatch makes the script exit with a non-zero status.

> diff --git a/tools/testing/selftests/net/veth.sh b/tools/testing/selftests/net/veth.sh
> index 64c2a5a59821d..5c1dbe1516bb4 100755
> --- a/tools/testing/selftests/net/veth.sh
> +++ b/tools/testing/selftests/net/veth.sh
> @@ -130,6 +130,7 @@ chk_channels() {
> echo " ok "
> else
> echo " fail rx:$rx:$cur_rx tx:$tx:$cur_tx combined:n/a:$cur_combined"
> + ret=1
> fi
> }
>

[Severity: Medium]
With this change, can a check whose result depends on the test environment
now fail the whole veth.sh run?

The "setting invalid channels nr" check expects a request for CPUS + 1 TX
queues to be rejected. CPUS comes from nproc:

readonly CPUS=`nproc`
...
ip netns exec $NS_DST ethtool -L veth$DST tx $((CPUS + 1)) 2>/dev/null
chk_channels "setting invalid channels nr" $DST $CUR_RX $CUR_TX

The veth queue limit is num_possible_cpus(), capped at 4096. It is not the
number of CPUs the process can use:

drivers/net/veth.c:veth_get_num_queues() {
/* enforce the same queue limit as rtnl_create_link */
int queues = num_possible_cpus();
...
}

veth_get_channels() reports dev->num_tx_queues as max_tx. The ethtool core
in net/ethtool/channels.c only rejects tx_count > max_tx.

nproc returns the number of CPUs the process can use. That can be smaller
than the number of possible CPUs on machines with hot-pluggable CPU slots,
or when the test runs under taskset or a restricted cpuset.

In those cases the request is valid. No XDP program is attached at that
point, so veth_set_channels() accepts it and real_num_tx_queues becomes
CPUS + 1. chk_channels() then sees cur_tx != $CUR_TX, and with this patch
veth.sh exits 1.

Before this patch, the mismatch only printed a fail line. The later patch
in the series ("selftests: net: veth: propagate bad-settings check
failures to exit status") does not change this check.

Could the out-of-range value come from the device's advertised maximum
instead of nproc? For example, the "Pre-set maximums" TX value from
ethtool -l, plus one.

--
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261116084107.6675-1-emmaonana18%40gmail.com