kernel/tools/testing/selftests/net/rtnetlink.sh, branch linux-5.1.y

selftests: rtnetlink: use internal netns switch for ip commands

2019-02-28T21:02:43Z

'ip' can switch network namespaces internally and then run a given command relative to that namespace without the need to fork and exec another ip instance. Update all references of the form: ip netns exec "$testns" ip ... to ip -netns "$testns" ... Signed-off-by: David Ahern Signed-off-by: David S. Miller

tools: selftests: rtnetlink: add testcases for vxlan flag sets

2019-02-26T16:54:37Z

This patch extends rtnetlink.sh to cover some vxlan flag netlink attribute sets. Signed-off-by: Roopa Prabhu Signed-off-by: David S. Miller

selftests: rtnetlink: Add a test case for multipath route get

2018-12-21T00:42:39Z

Without previous patch a warning would be generated upon multipath route get when FIB multipath hash policy is to use a 5-tuple for multipath hash calculation. Signed-off-by: Ido Schimmel Signed-off-by: David S. Miller

selftests: rtnetlink.sh: add testcase for neigh get

2018-12-19T21:37:34Z

Signed-off-by: Roopa Prabhu Reviewed-by: David Ahern Signed-off-by: David S. Miller

selftests: net: rtnetlink.sh: add fdb get test

2018-12-16T22:42:34Z

tests the below three cases of bridge fdb get: [bridge, mac, vlan] [bridge_port, mac, vlan, flags=[NTF_MASTER]] [vxlandev, mac, flags=NTF_SELF] depends on iproute2 support for bridge fdb get. Signed-off-by: Roopa Prabhu Signed-off-by: David S. Miller

selftests: rtnetlink.sh explicitly requires bash.

2018-10-11T17:19:46Z

the script rtnetlink.sh requires a bash-only features (sleep with sub-second precision). This may cause random test failure if the default shell is not bash. Address the above explicitly requiring bash as the script interpreter. Fixes: 33b01b7b4f19 ("selftests: add rtnetlink test script") Signed-off-by: Paolo Abeni Signed-off-by: David S. Miller

selftests: rtnetlink: add ipsec offload API test

2018-06-28T07:10:08Z

Using the netdevsim as a device for testing, try out the XFRM commands for setting up IPsec hardware offloads. Signed-off-by: Shannon Nelson Signed-off-by: David S. Miller

selftests: rtnetlink: use dummydev as a test device

2018-06-28T07:10:08Z

We really shouldn't mess with local system settings, so let's use the already created dummy device instead for ipsec testing. Oh, and let's put the temp file into a proper directory. Signed-off-by: Shannon Nelson Signed-off-by: David S. Miller

selftests: rtnetlink: clear the return code at start of ipsec test

2018-06-28T07:10:07Z

Following the custom from the other functions, clear the global ret code before starting the test so as to not have previously failed tests cause us to thing this test has failed. Reported-by: Anders Roxell Signed-off-by: Shannon Nelson Signed-off-by: David S. Miller

selftests: rtnetlink: use a local IP address for IPsec tests

2018-06-22T04:47:55Z

Find an IP address on this machine to use as a source IP, and make up a destination IP address based on the source IP. No actual messages will be sent, just a couple of IPsec rules are created and deleted. Fixes: 5e596ee171ba ("selftests: add xfrm state-policy-monitor to rtnetlink.sh") Reported-by: Anders Roxell Signed-off-by: Shannon Nelson Signed-off-by: David S. Miller