kernel/linux.git/tools/testing/selftests/net/forwarding/lib.sh, branch v4.19.237

selftests: forwarding: Have lldpad_app_wait_set() wait for unknown, too

2019-11-24T07:21:02+00:00

[ Upstream commit 372809055f6c830ff978564e09f58bcb9e9b937c ] Immediately after mlxsw module is probed and lldpad started, added APP entries are briefly in "unknown" state before becoming "pending". That's the state that lldpad_app_wait_set() typically sees, and since there are no pending entries at that time, it bails out. However the entries have not been pushed to the kernel yet at that point, and thus the test case fails. Fix by waiting for both unknown and pending entries to disappear before proceeding. Fixes: d159261f3662 ("selftests: mlxsw: Add test for trust-DSCP") Signed-off-by: Petr Machata Signed-off-by: Ido Schimmel Signed-off-by: David S. Miller Signed-off-by: Sasha Levin

selftests: forwarding: Move DSCP capture to lib.sh

2018-08-01T16:52:30+00:00

dscp_capture_install() and dscp_capture_uninstall() are going to be useful for a test added by a following patch, move them therefore to lib.sh together with related helpers. While doing so, change the rule preference from mere DSCP value to DSCP+100 in order to support adding captures of packets with DSCP of 0. Signed-off-by: Petr Machata Reviewed-by: Ido Schimmel Signed-off-by: David S. Miller

selftests: forwarding: Move lldpad waiting to lib.sh

2018-08-01T16:52:30+00:00

The function lldpad_wait() will be useful for a test added by a following patch. Likewise would the "sleep 5" with its extensive comment. Therefore move lldpad_wait() to lib.sh in order to allow reuse. Rename it to lldpad_app_wait_set() to recognize that what this is intended to wait on are the pending APP sets. For the sleeping, add a function lldpad_app_wait_del(). That will serve to hold the related explanatory comment (which edit for clarity), and as a token in the caller to identify the sites where this sort of waiting takes place. That will serve when/if a better way to handle this business is found. Signed-off-by: Petr Machata Reviewed-by: Ido Schimmel Signed-off-by: David S. Miller

selftests: forwarding: Introduce $ARPING

2018-07-30T16:47:21+00:00

Instead of relying on "arping" being installed everywhere under that name, introduce a variable $ARPING like the other tools do. Convert an existing test, mirror_gre_vlan_bridge_1q.sh to require_command $ARPING and then invoke arping through the variable. Signed-off-by: Petr Machata Signed-off-by: David S. Miller

selftests: forwarding: lib: Support team devices

2018-07-30T16:47:21+00:00

Add team_create() and team_destroy() to manage team netdevices. Signed-off-by: Petr Machata Signed-off-by: David S. Miller

selftests: forwarding: lib: Add require_command()

2018-07-30T16:47:21+00:00

The logic for testing whether a certain command is available is used several times in the current code base. The tests in follow-up patches add more requirements like that. Therefore extract the logic into a named function, require_command(), that can be used directly from lib.sh as well as from any test that wishes to declare dependence on some command. Signed-off-by: Petr Machata Signed-off-by: David S. Miller

selftests: forwarding: add tests for TC chains creation adn destruction

2018-07-24T03:44:13+00:00

Add basic sanity tests for TC chains. Signed-off-by: Jiri Pirko Signed-off-by: David S. Miller

selftests: forwarding: move shblock tc support check to a separate helper

2018-07-24T03:44:13+00:00

The shared block support is only needed for tc_shblock.sh. No need to require that for other test. Signed-off-by: Jiri Pirko Signed-off-by: David S. Miller

selftests: forwarding: lib: extract ping and ping6 so they can be reused

2018-07-04T12:40:02+00:00

Extract ping and ping6 command execution so the return value can be checked by the caller, this is needed for port isolation tests that are intended to fail. Signed-off-by: Nikolay Aleksandrov Signed-off-by: David S. Miller

selftests: forwarding: lib: Parameterize NUM_NETIFS in two functions

2018-06-30T13:06:15+00:00

setup_wait() and tc_offload_check() both assume that all NUM_NETIFS interfaces are relevant for a given test. However, the scale test script acts as an umbrella for a number of sub-tests, some of which may not require all the interfaces. Thus it's suboptimal for tc_offload_check() to query all the interfaces. In case of setup_wait() it's incorrect, because the sub-test in question of course doesn't configure any interfaces beyond what it needs, and setup_wait() then ends up waiting indefinitely for the extraneous interfaces to come up. For that reason, give setup_wait() and tc_offload_check() an optional parameter with a number of interfaces to probe. Fall back to global NUM_NETIFS if the parameter is not given. Signed-off-by: Petr Machata Reviewed-by: Yuval Mintz Signed-off-by: David S. Miller