kernel/linux.git/tools/testing/selftests/tc-testing, branch v4.17.5

tc-testing: fix tdc tests for 'bpf' action

2018-05-10T21:28:02+00:00

- correct a typo in the value of 'matchPattern' of test 282d, potentially causing false negative - allow errors when 'teardown' executes '$TC action flush action bpf' in test 282d, to fix false positive when it is run with act_bpf unloaded - correct the value of 'matchPattern' in test e939, causing false positive in case the BPF JIT is enabled Fixes: 440ea4ae1828 ("tc-testing: add selftests for 'bpf' action") Signed-off-by: Davide Caratti Acked-by: Lucas Bates Signed-off-by: David S. Miller

tc-testing: Add newline when writing test case files

2018-03-30T18:22:51+00:00

When using the -i feature to generate random ID numbers for test cases in tdc, the function that writes the JSON to file doesn't add a newline character to the end of the file, so we have to add our own. Signed-off-by: Lucas Bates Signed-off-by: David S. Miller

tc-testing: add connmark action tests

2018-03-30T16:58:23+00:00

Signed-off-by: Roman Mashak Signed-off-by: David S. Miller

tc-testing: Correct compound statements for namespace execution

2018-03-27T14:52:07+00:00

If tdc is executing test cases inside a namespace, only the first command in a compound statement will be executed inside the namespace by tdc. As a result, the subsequent commands are not executed inside the namespace and the test will fail. Example: for i in {x..y}; do args="foo"; done && tc actions add $args The namespace execution feature will prepend 'ip netns exec' to the command: ip netns exec tcut for i in {x..y}; do args="foo"; done && \ tc actions add $args So the actual tc command is not parsed by the shell as being part of the namespace execution. Enclosing these compound statements inside a bash invocation with proper escape characters resolves the problem by creating a subshell inside the namespace. Signed-off-by: Lucas Bates Signed-off-by: David S. Miller

tc-testing: updated police, mirred, skbedit and skbmod with more tests

2018-03-26T00:41:46+00:00

Added extra test cases for control actions (reclassify, pipe etc.), cookies, max index value and police args sanity check. Signed-off-by: Roman Mashak Signed-off-by: David S. Miller

tc-testing: add selftests for 'bpf' action

2018-03-23T16:58:52+00:00

Test d959: Add cBPF action with valid bytecode Test f84a: Add cBPF action with invalid bytecode Test e939: Add eBPF action with valid object-file Test 282d: Add eBPF action with invalid object-file Test d819: Replace cBPF bytecode and action control Test 6ae3: Delete cBPF action Test 3e0d: List cBPF actions Test 55ce: Flush BPF actions Test ccc3: Add cBPF action with duplicate index Test 89c7: Add cBPF action with invalid index Test 7ab9: Add cBPF action with cookie Changes since v1: - use index=2^32-1 in test ccc3, add tests 7a89, 89c7 (thanks Roman Mashak) - added test 282d Signed-off-by: Davide Caratti Signed-off-by: David S. Miller

tc-testing: updated gact tests with batch test cases

2018-03-13T01:08:54+00:00

Signed-off-by: Roman Mashak Signed-off-by: David S. Miller

tc-testing: add TC vlan action tests

2018-03-13T01:07:48+00:00

Signed-off-by: Roman Mashak Signed-off-by: David S. Miller

tools: tc-testing: Can pause just before post-suite

2018-03-09T16:22:18+00:00

With option -P, the test script will pause just before the post_suite functions are called. This allows the tester to inspect the system before it is torn down. Signed-off-by: Brenda J. Butler Signed-off-by: David S. Miller

tools: tc-testing: Can refer to $TESTID in test spec

2018-03-09T16:21:55+00:00

When processing the commands in the test cases, substitute the test id for $TESTID. This helps to make more flexible tests. For example, the testid can be given as a command line argument. As an example, if we wish to save the test output to a file named for the test case, we can write in the test case: "cmdUnderTest": "some test command | tee -a $TESTID.out" Signed-off-by: Brenda J. Butler Signed-off-by: David S. Miller