selftests/net: plug rxtimestamp test into kselftest framework
authortannerlove <tannerlove@google.com>
Mon, 22 Jun 2020 17:43:24 +0000 (13:43 -0400)
committerDavid S. Miller <davem@davemloft.net>
Wed, 24 Jun 2020 03:36:46 +0000 (20:36 -0700)
commit0558c396040734bc1d361919566a581fd41aa539
tree0c661cb487d5562da742284c0ea39a37475a584d
parent547030c8e663520348557a5c7ed1eacf72e6bf86
selftests/net: plug rxtimestamp test into kselftest framework

Run rxtimestamp as part of TEST_PROGS. Analogous to other tests, add
new rxtimestamp.sh wrapper script, so that the test runs isolated
from background traffic in a private network namespace.

Also ignore failures of test case #6 by default. This case verifies
that a receive timestamp is not reported if timestamp reporting is
enabled for a socket, but generation is disabled. Receive timestamp
generation has to be enabled globally, as no associated socket is
known yet. A background process that enables rx timestamp generation
therefore causes a false positive. Ntpd is one example that does.

Add a "--strict" option to cause failure in the event that any test
case fails, including test #6. This is useful for environments that
are known to not have such background processes.

Tested:
make -C tools/testing/selftests TARGETS="net" run_tests

Signed-off-by: Tanner Love <tannerlove@google.com>
Acked-by: Willem de Bruijn <willemb@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
tools/testing/selftests/net/Makefile
tools/testing/selftests/net/rxtimestamp.c
tools/testing/selftests/net/rxtimestamp.sh [new file with mode: 0755]