wireguard-linux/tools/testing, branch backport-5.4.y

wireguard: selftests: use microvm on x86

2022-07-07T11:26:46Z

commit b83fdcd9fb8ad7e59f4188ba9ec221917f463a17 upstream. This makes for faster tests, faster compile time, and allows us to ditch ACPI finally. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: always call kernel makefile

2022-07-07T11:26:46Z

commit 1a087eec257154e26a81a7a0a15380d7a2431765 upstream. These selftests are used for much more extensive changes than just the wireguard source files. So always call the kernel's build file, which will do something or nothing after checking the whole tree, per usual. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: set fake real time in init

2022-07-07T11:26:46Z

commit 829be057dbc1e71383b8d7de8edb31dcf07b4aa0 upstream. Not all platforms have an RTC, and rather than trying to force one into each, it's much easier to just set a fixed time. This is necessary because WireGuard's latest handshakes parameter is returned in wallclock time, and if the system time isn't set, and the system is really fast, then this returns 0, which trips the test. Turning this on requires setting CONFIG_COMPAT_32BIT_TIME=y, as musl doesn't support settimeofday without it. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: set panic_on_warn=1 from cmdline

2022-07-07T11:26:46Z

commit 3fc1b11e5d7278437bdfff0e01f51e777eefb222 upstream. Rather than setting this once init is running, set panic_on_warn from the kernel command line, so that it catches splats from WireGuard initialization code and the various crypto selftests. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: bump package deps

2022-07-07T11:26:46Z

commit a6b8ea9144340c0aaa66c817a3bbb6bca47f0321 upstream. Use newer, more reliable package dependencies. These should hopefully reduce flakes. However, we keep the old iputils package, as it accumulated bugs after resulting in flakes on slow machines. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: restore support for ccache

2022-07-07T11:26:46Z

commit d261ba6aa411e03c27da266b7df4bef771e8105e upstream. When moving to non-system toolchains, we inadvertantly killed the ability to use ccache. So instead, build ccache support into the test harness directly. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: use newer toolchains to fill out architectures

2022-07-07T11:26:46Z

commit d5d9b29bc963cc084c5c0f3a7c28e2632a22e0c4 upstream. Rather than relying on the system to have cross toolchains available, simply download musl.cc's ones and use that libc.so, and then we use it to fill in a few missing platforms, such as s390x and powerpc64. Also, on arm, use virtio's serial port to avoid having to patch QEMU. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: limit parallelism to $(nproc) tests at once

2022-07-07T11:26:46Z

commit 39f02bf1e5ce9d72045de01e3d618ade1067158c upstream. The parallel tests were added to catch queueing issues from multiple cores. But what happens in reality when testing tons of processes is that these separate threads wind up fighting with the scheduler, and we wind up with contention in places we don't care about that decrease the chances of hitting a bug. So just do a test with the number of CPU cores, rather than trying to scale up arbitrarily. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: make routing loop test non-fatal

2022-07-07T11:26:46Z

commit ae2de669c14a18b5144cdacf49933ad400ed7e1c upstream. I hate to do this, but I still do not have a good solution to actually fix this bug across architectures. So just disable it for now, so that the CI can still deliver actionable results. This commit adds a large red warning, so that at least the failure isn't lost forever, and hopefully this can be revisited down the line. Link: https://lore.kernel.org/netdev/CAHmME9pv1x6C4TNdL6648HydD8r+txpV4hTUXOBVkrapBXH4QQ@mail.gmail.com/ Link: https://lore.kernel.org/netdev/YmszSXueTxYOC41G@zx2c4.com/ Link: https://lore.kernel.org/wireguard/CAHmME9rNnBiNvBstb7MPwK-7AmAN0sOfnhdR=eeLrowWcKxaaQ@mail.gmail.com/ Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld

wireguard: selftests: enable ACPI for SMP

2022-07-07T11:26:45Z

commit 00f3d2ed9dac8fc8674a021765a0772f74c6127b upstream. It turns out that by having CONFIG_ACPI=n, we've been failing to boot additional CPUs, and so these systems were functionally UP. The code bloat is unfortunate for build times, but I don't see an alternative. So this commit sets CONFIG_ACPI=y for x86_64 and i686 configs. Signed-off-by: Jason A. Donenfeld Signed-off-by: Jakub Kicinski Signed-off-by: Jason A. Donenfeld