August 2023 - Linux-kselftest-mirror

[PATCH v1] selftests/landlock: Fix a resource leak

by Ding Xiang

The opened file should be closed before return, otherwise resource leak will occur Signed-off-by: Ding Xiang <dingxiang(a)cmss.chinamobile.com> --- tools/testing/selftests/landlock/fs_test.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tools/testing/selftests/landlock/fs_test.c b/tools/testing/selftests/landlock/fs_test.c index 83d565569512..251594306d40 100644 --- a/tools/testing/selftests/landlock/fs_test.c +++ b/tools/testing/selftests/landlock/fs_test.c @@ -113,7 +113,7 @@ static bool supports_filesystem(const char *const filesystem) { char str[32]; int len; - bool res; + bool res = true; FILE *const inf = fopen("/proc/filesystems", "r"); /* @@ -125,14 +125,16 @@ static bool supports_filesystem(const char *const filesystem) /* filesystem can be null for bind mounts. */ if (!filesystem) - return true; + goto out; len = snprintf(str, sizeof(str), "nodev\t%s\n", filesystem); if (len >= sizeof(str)) /* Ignores too-long filesystem names. */ - return true; + goto out; res = fgrep(inf, str); + +out: fclose(inf); return res; } -- 2.38.1

1 year, 3 months

2
1
0 0

[PATCH net v3 0/3] Avoid TCP resets when using ECMP for load-balancing between multiple servers.

by Sriram Yagnaraman

All packets in the same flow (L3/L4 depending on multipath hash policy) should be directed to the same target, but after [0]/[1] we see stray packets directed towards other targets. This, for instance, causes RST to be sent on TCP connections. The first two patches solve the problem by ignoring route hints for destinations that are part of multipath group, by using new SKB flags for IPv4 and IPv6. The third patch is a selftest that tests the scenario. Thanks to Ido, for reviewing and suggesting a way forward in [2] and also suggesting how to write a selftest for this. v2->v3: - Add NULL check for skb in fib6_select_path (Ido Schimmel) - Use fib_tests.sh for selftest instead of the forwarding suite (Ido Schimmel) v1->v2: - Update to commit messages describing the solution (Ido Schimmel) - Use perf stat to count fib table lookups in selftest (Ido Schimmel) Sriram Yagnaraman (3): ipv4: ignore dst hint for multipath routes ipv6: ignore dst hint for multipath routes selftests: fib_tests: Add multipath list receive tests include/linux/ipv6.h | 1 + include/net/ip.h | 1 + net/ipv4/ip_input.c | 3 +- net/ipv4/route.c | 1 + net/ipv6/ip6_input.c | 3 +- net/ipv6/route.c | 3 + tools/testing/selftests/net/fib_tests.sh | 150 ++++++++++++++++++++++- 7 files changed, 159 insertions(+), 3 deletions(-) -- 2.34.1

1 year, 3 months

4
12
0 0

[PATCH] selftests: static_keys: fix messages

by Javier Carrasco

Use "static_keys" (name of the test itself) consistently instead of mixing "static_key" and "static_keys" at the beginning of the messages in the test_static_keys script. Signed-off-by: Javier Carrasco <javier.carrasco.cruz(a)gmail.com> --- This single-patch series fixes a minor inconsistency in the 'test_static_keys' script from the static_keys selftest. As a general rule, the selftest name is provided at the beginning of every log message. Apply the selftest name for all log messages consequently. --- tools/testing/selftests/static_keys/test_static_keys.sh | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tools/testing/selftests/static_keys/test_static_keys.sh b/tools/testing/selftests/static_keys/test_static_keys.sh index fc9f8cde7d42..3b0f17b81ac2 100755 --- a/tools/testing/selftests/static_keys/test_static_keys.sh +++ b/tools/testing/selftests/static_keys/test_static_keys.sh @@ -6,18 +6,18 @@ ksft_skip=4 if ! /sbin/modprobe -q -n test_static_key_base; then - echo "static_key: module test_static_key_base is not found [SKIP]" + echo "static_keys: module test_static_key_base is not found [SKIP]" exit $ksft_skip fi if ! /sbin/modprobe -q -n test_static_keys; then - echo "static_key: module test_static_keys is not found [SKIP]" + echo "static_keys: module test_static_keys is not found [SKIP]" exit $ksft_skip fi if /sbin/modprobe -q test_static_key_base; then if /sbin/modprobe -q test_static_keys; then - echo "static_key: ok" + echo "static_keys: ok" /sbin/modprobe -q -r test_static_keys /sbin/modprobe -q -r test_static_key_base else @@ -25,6 +25,6 @@ if /sbin/modprobe -q test_static_key_base; then /sbin/modprobe -q -r test_static_key_base fi else - echo "static_key: [FAIL]" + echo "static_keys: [FAIL]" exit 1 fi --- base-commit: 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5 change-id: 20230830-feature-static_keys_selftest_messages-d43d67db7974 Best regards, -- Javier Carrasco <javier.carrasco.cruz(a)gmail.com>

1 year, 3 months

1
0
0 0

[RFC PATCH] kunit: Fix test log size limit too low for some tests

by Janusz Krzysztofik

Now we have memory space available to a kunit test case log exposed via debugfs limited to 2048 bytes, while some parametrized test cases, e.g., drm_framebuffer.drm_test_framebuffer_create, need more. For this reason, debugfs results from affected test cases get truncated silently, and external tools that rely on parsing of debugfs results can fail. Increase kunit test case log size limit to 4096 bytes. Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik(a)linux.intel.com> --- include/kunit/test.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/kunit/test.h b/include/kunit/test.h index d33114097d0d0..d20eb1884edfa 100644 --- a/include/kunit/test.h +++ b/include/kunit/test.h @@ -34,7 +34,7 @@ DECLARE_STATIC_KEY_FALSE(kunit_running); struct kunit; /* Size of log associated with test. */ -#define KUNIT_LOG_SIZE 2048 +#define KUNIT_LOG_SIZE 4096 /* Maximum size of parameter description string. */ #define KUNIT_PARAM_DESC_SIZE 128 -- 2.41.0

1 year, 3 months

2
2
0 0

[PATCH net v4 0/3] Avoid TCP resets when using ECMP for load-balancing between multiple servers.

by Sriram Yagnaraman

All packets in the same flow (L3/L4 depending on multipath hash policy) should be directed to the same target, but after [0]/[1] we see stray packets directed towards other targets. This, for instance, causes RST to be sent on TCP connections. The first two patches solve the problem by ignoring route hints for destinations that are part of multipath group, by using new SKB flags for IPv4 and IPv6. The third patch is a selftest that tests the scenario. Thanks to Ido, for reviewing and suggesting a way forward in [2] and also suggesting how to write a selftest for this. v3->v4: - Remove single path test - Rebase to latest v2->v3: - Add NULL check for skb in fib6_select_path (Ido Schimmel) - Use fib_tests.sh for selftest instead of the forwarding suite (Ido Schimmel) v1->v2: - Update to commit messages describing the solution (Ido Schimmel) - Use perf stat to count fib table lookups in selftest (Ido Schimmel) Sriram Yagnaraman (3): ipv4: ignore dst hint for multipath routes ipv6: ignore dst hint for multipath routes selftests: fib_tests: Add multipath list receive tests include/linux/ipv6.h | 1 + include/net/ip.h | 1 + net/ipv4/ip_input.c | 3 +- net/ipv4/route.c | 1 + net/ipv6/ip6_input.c | 3 +- net/ipv6/route.c | 3 + tools/testing/selftests/net/fib_tests.sh | 158 ++++++++++++++++++++++- 7 files changed, 167 insertions(+), 3 deletions(-) -- 2.34.1

1 year, 3 months

2
4
0 0

[PATCH] selftests/landlock: Fix a resource leak

by Ding Xiang

The opened file should be closed before return, otherwise resource leak will occur Signed-off-by: Ding Xiang <dingxiang(a)cmss.chinamobile.com> --- tools/testing/selftests/landlock/fs_test.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/landlock/fs_test.c b/tools/testing/selftests/landlock/fs_test.c index 83d565569512..687a66ea9799 100644 --- a/tools/testing/selftests/landlock/fs_test.c +++ b/tools/testing/selftests/landlock/fs_test.c @@ -124,13 +124,17 @@ static bool supports_filesystem(const char *const filesystem) return true; /* filesystem can be null for bind mounts. */ - if (!filesystem) + if (!filesystem) { + fclose(inf); return true; + } len = snprintf(str, sizeof(str), "nodev\t%s\n", filesystem); - if (len >= sizeof(str)) + if (len >= sizeof(str)) { + fclose(inf); /* Ignores too-long filesystem names. */ return true; + } res = fgrep(inf, str); fclose(inf); -- 2.38.1

1 year, 3 months

2
1
0 0

[PATCH 0/2] nolibc: remove reliance on system headers

by Thomas Weißschuh

This was prompted by the discussion about output directory support with O=. It seems sometimes we were pulling in system headers making testing annoying and unreliable. Signed-off-by: Thomas Weißschuh <linux(a)weissschuh.net> --- Thomas Weißschuh (2): tools/nolibc: add stdarg.h header selftests/nolibc: use -nostdinc for nolibc-test tools/include/nolibc/Makefile | 1 + tools/include/nolibc/stdarg.h | 16 ++++++++++++++++ tools/testing/selftests/nolibc/Makefile | 2 +- 3 files changed, 18 insertions(+), 1 deletion(-) --- base-commit: 556fb7131e03b0283672fb40f6dc2d151752aaa7 change-id: 20230827-nolibc-nostdinc-203908130d67 Best regards, -- Thomas Weißschuh <linux(a)weissschuh.net>

1 year, 3 months

2
10
0 0

[PATCH v3 0/9] kunit: Add test attributes API

by Rae Moar

Hello everyone, This patch series adds a test attributes framework to KUnit. There has been interest in filtering out "slow" KUnit tests. Most notably, a new config, CONFIG_MEMCPY_SLOW_KUNIT_TEST, has been added to exclude a particularly slow memcpy test (https://lore.kernel.org/all/20230118200653.give.574-kees@kernel.org/). This attributes framework can be used to save and access test associated data, including whether a test is slow. These attributes are reportable (via KTAP and command line output) and are also filterable. This framework is designed to allow for the addition of other attributes in the future. These attributes could include whether the test can be run concurrently, test file path, etc. To try out the framework I suggest running: "./tools/testing/kunit/kunit.py run --filter speed!=slow" This patch series was originally sent out as an RFC. Here is a link to the RFC v2: https://lore.kernel.org/all/20230707210947.1208717-1-rmoar@google.com/ Thanks! Rae Rae Moar (9): kunit: Add test attributes API structure kunit: Add speed attribute kunit: Add module attribute kunit: Add ability to filter attributes kunit: tool: Add command line interface to filter and report attributes kunit: memcpy: Mark tests as slow using test attributes kunit: time: Mark test as slow using test attributes kunit: add tests for filtering attributes kunit: Add documentation of KUnit test attributes Documentation/dev-tools/kunit/run_wrapper.rst | 12 + .../dev-tools/kunit/running_tips.rst | 166 +++++++ include/kunit/attributes.h | 50 +++ include/kunit/test.h | 70 ++- kernel/time/time_test.c | 2 +- lib/Kconfig.debug | 3 + lib/kunit/Makefile | 3 +- lib/kunit/attributes.c | 418 ++++++++++++++++++ lib/kunit/executor.c | 114 ++++- lib/kunit/executor_test.c | 128 +++++- lib/kunit/kunit-example-test.c | 9 + lib/kunit/test.c | 27 +- lib/memcpy_kunit.c | 8 +- tools/testing/kunit/kunit.py | 70 ++- tools/testing/kunit/kunit_kernel.py | 8 +- tools/testing/kunit/kunit_parser.py | 11 +- tools/testing/kunit/kunit_tool_test.py | 39 +- 17 files changed, 1062 insertions(+), 76 deletions(-) create mode 100644 include/kunit/attributes.h create mode 100644 lib/kunit/attributes.c base-commit: 64bd4641310c41a1ecf07c13c67bc0ed61045dfd -- 2.41.0.487.g6d72f3e995-goog

1 year, 3 months

4
17
0 0

[RFC v2 0/2] CPU-Idle latency selftest framework

by Aboorva Devarajan

Changelog: v1 -> v2 * Rebased on v6.5-rc6 * Moved the test directory to powerpc debugfs * Minimal code refactoring RFC v1: https://lore.kernel.org/all/20210611124154.56427-1-psampat@linux.ibm.com/ Other related RFC: https://lore.kernel.org/all/20210430082804.38018-1-psampat@linux.ibm.com/ Userspace selftest: https://lkml.org/lkml/2020/9/2/356 ---- A kernel module + userspace driver to estimate the wakeup latency caused by going into stop states. The motivation behind this program is to find significant deviations behind advertised latency and residency values. The patchset measures latencies for two kinds of events. IPIs and Timers As this is a software-only mechanism, there will be additional latencies of the kernel-firmware-hardware interactions. To account for that, the program also measures a baseline latency on a 100 percent loaded CPU and the latencies achieved must be in view relative to that. To achieve this, we introduce a kernel module and expose its control knobs through the debugfs interface that the selftests can engage with. The kernel module provides the following interfaces within /sys/kernel/debug/powerpc/latency_test/ for, IPI test: ipi_cpu_dest = Destination CPU for the IPI ipi_cpu_src = Origin of the IPI ipi_latency_ns = Measured latency time in ns Timeout test: timeout_cpu_src = CPU on which the timer to be queued timeout_expected_ns = Timer duration timeout_diff_ns = Difference of actual duration vs expected timer Sample output is as follows: # --IPI Latency Test--- # Baseline Avg IPI latency(ns): 2720 # Observed Avg IPI latency(ns) - State snooze: 2565 # Observed Avg IPI latency(ns) - State stop0_lite: 3856 # Observed Avg IPI latency(ns) - State stop0: 3670 # Observed Avg IPI latency(ns) - State stop1: 3872 # Observed Avg IPI latency(ns) - State stop2: 17421 # Observed Avg IPI latency(ns) - State stop4: 1003922 # Observed Avg IPI latency(ns) - State stop5: 1058870 # # --Timeout Latency Test-- # Baseline Avg timeout diff(ns): 1435 # Observed Avg timeout diff(ns) - State snooze: 1709 # Observed Avg timeout diff(ns) - State stop0_lite: 2028 # Observed Avg timeout diff(ns) - State stop0: 1954 # Observed Avg timeout diff(ns) - State stop1: 1895 # Observed Avg timeout diff(ns) - State stop2: 14556 # Observed Avg timeout diff(ns) - State stop4: 873988 # Observed Avg timeout diff(ns) - State stop5: 959137 Aboorva Devarajan (2): powerpc/cpuidle: cpuidle wakeup latency based on IPI and timer events powerpc/selftest: Add support for cpuidle latency measurement arch/powerpc/Kconfig.debug | 10 + arch/powerpc/kernel/Makefile | 1 + arch/powerpc/kernel/test_cpuidle_latency.c | 156 ++++++ tools/testing/selftests/powerpc/Makefile | 1 + .../powerpc/cpuidle_latency/.gitignore | 2 + .../powerpc/cpuidle_latency/Makefile | 6 + .../cpuidle_latency/cpuidle_latency.sh | 443 ++++++++++++++++++ .../powerpc/cpuidle_latency/settings | 1 + 8 files changed, 620 insertions(+) create mode 100644 arch/powerpc/kernel/test_cpuidle_latency.c create mode 100644 tools/testing/selftests/powerpc/cpuidle_latency/.gitignore create mode 100644 tools/testing/selftests/powerpc/cpuidle_latency/Makefile create mode 100755 tools/testing/selftests/powerpc/cpuidle_latency/cpuidle_latency.sh create mode 100644 tools/testing/selftests/powerpc/cpuidle_latency/settings -- 2.25.1

1 year, 3 months

2
3
0 0

selftests: net: pmtu.sh: Unable to handle kernel paging request at virtual address

by Naresh Kamboju

The selftests: net: pmtu.sh running on Linux next got this kernel panic on qemu-arm64. logs: ==== [ 0.000000] Linux version 6.5.0 (tuxmake@tuxmake) (Debian clang version 18.0.0 (++20230822112105+841c4dc7e51e-1~exp1~20230822112223.851), Debian LLD 18.0.0) #1 SMP PREEMPT @1693176139 ... # selftests: net: pmtu.sh # TEST: ipv4: PMTU exceptions [ OK ] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] # TEST: ipv6: PMTU exceptions [ OK ] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] ... # TEST: vti4: PMTU exceptions, routed (ESP-in-UDP) [FAIL] # PMTU exception wasn't created after exceeding PMTU (IP payload length 1438) # ./pmtu.sh: 938: kill: No such process # # ./pmtu.sh: 938: kill: No such process # <47>[ 366.411270] systemd-journald[84]: Sent WATCHDOG=1 notification. # TEST: vti4: default MTU assignment [ OK ] # TEST: vti6: default MTU assignment [ OK ] # TEST: vti4: MTU setting on link creation [ OK ] # TEST: vti6: MTU setting on link creation [ OK ] # TEST: vti6: MTU changes on link changes [ OK ] # TEST: ipv4: cleanup of cached exceptions [ OK ] # TEST: ipv4: cleanup of cached exceptions - nexthop objects [ OK ] # TEST: ipv6: cleanup of cached exceptions [ OK ] # TEST: ipv6: cleanup of cached exceptions - nexthop objects [ OK ] <1>[ 398.987591] Unable to handle kernel paging request at virtual address ffff5dbb8189f000 <1>[ 398.988469] Mem abort info: <1>[ 398.988712] ESR = 0x0000000097b58004 <1>[ 398.989264] EC = 0x25: DABT (current EL), IL = 32 bits <1>[ 398.989893] SET = 0, FnV = 0 <1>[ 398.990312] EA = 0, S1PTW = 0 <1>[ 398.990768] FSC = 0x04: level 0 translation fault <1>[ 398.992330] Data abort info: <1>[ 398.992591] Access size = 4 byte(s) <1>[ 398.992811] SSE = 1, SRT = 21 <1>[ 398.993008] SF = 1, AR = 0 <1>[ 398.993243] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 <1>[ 398.993601] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 <1>[ 398.994094] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000041d49000 <1>[ 398.994603] [ffff5dbb8189f000] pgd=0000000000000000, p4d=0000000000000000 <0>[ 398.995464] Internal error: Oops: 0000000097b58004 [#1] PREEMPT SMP <4>[ 398.996177] Modules linked in: fou6 sit fou bridge stp llc vxlan ip6_udp_tunnel udp_tunnel act_csum libcrc32c act_pedit cls_flower sch_prio veth vrf macvtap macvlan tap crct10dif_ce sm3_ce sm3 sha3_ce sha512_ce sha512_arm64 fuse drm dm_mod ip_tables x_tables [last unloaded: test_blackhole_dev] <4>[ 398.999384] CPU: 1 PID: 132 Comm: kworker/u4:3 Not tainted 6.5.0 #1 <4>[ 399.000045] Hardware name: linux,dummy-virt (DT) <4>[ 399.001079] Workqueue: netns cleanup_net <4>[ 399.002441] pstate: 824000c9 (Nzcv daIF +PAN -UAO +TCO -DIT -SSBS BTYPE=--) <4>[ 399.003881] pc : percpu_counter_add_batch+0x28/0xd0 <4>[ 399.004637] lr : dst_destroy+0x44/0x1e4 <4>[ 399.004904] sp : ffff80008000be70 <4>[ 399.005864] x29: ffff80008000be70 x28: ffffa2457df6ea40 x27: ffffa2457df24008 <4>[ 399.006586] x26: ffffa2457dffa000 x25: 000000000000000a x24: 0000000000000002 <4>[ 399.007360] x23: 0000000000000000 x22: 000000000000000a x21: ffff0000c0e90ec0 <4>[ 399.008276] x20: 0000000000000000 x19: ffff0000c4f83440 x18: 0000000000000000 <4>[ 399.009327] x17: ffff5dbb8189f000 x16: ffff800080008000 x15: 0000000000000010 <4>[ 399.009653] x14: 0000000000000010 x13: 0000000000000004 x12: 0000000000000701 <4>[ 399.010159] x11: 0000000000000001 x10: fffffc00030c7260 x9 : ffff5dbb8189f000 <4>[ 399.010742] x8 : 0000000000000000 x7 : 7f7f7f7f7f7f7f7f x6 : fefefefefefefeff <4>[ 399.012056] x5 : 000000000010000e x4 : fffffc00030c7260 x3 : 000000000010000e <4>[ 399.013082] x2 : 0000000000000020 x1 : ffffffffffffffff x0 : ffff0000c4f83440 <4>[ 399.014716] Call trace: <4>[ 399.015702] percpu_counter_add_batch+0x28/0xd0 <4>[ 399.016399] dst_destroy+0x44/0x1e4 <4>[ 399.016681] dst_destroy_rcu+0x14/0x20 <4>[ 399.017009] rcu_core+0x2d0/0x5e0 <4>[ 399.017311] rcu_core_si+0x10/0x1c <4>[ 399.017609] __do_softirq+0xd4/0x23c <4>[ 399.017991] ____do_softirq+0x10/0x1c <4>[ 399.018320] call_on_irq_stack+0x24/0x4c <4>[ 399.018723] do_softirq_own_stack+0x1c/0x28 <4>[ 399.022639] __irq_exit_rcu+0x6c/0xcc <4>[ 399.023434] irq_exit_rcu+0x10/0x1c <4>[ 399.023962] el1_interrupt+0x8c/0xc0 <4>[ 399.024810] el1h_64_irq_handler+0x18/0x24 <4>[ 399.025324] el1h_64_irq+0x64/0x68 <4>[ 399.025612] _raw_spin_lock_bh+0x0/0x6c <4>[ 399.026102] cleanup_net+0x280/0x45c <4>[ 399.026403] process_one_work+0x1d4/0x310 <4>[ 399.027140] worker_thread+0x248/0x470 <4>[ 399.027621] kthread+0xfc/0x184 <4>[ 399.028068] ret_from_fork+0x10/0x20 <0>[ 399.029333] Code: d50343df aa0003f3 f9401008 d53cd049 (b8a86935) <4>[ 399.030578] ---[ end trace 0000000000000000 ]--- <0>[ 399.031422] Kernel panic - not syncing: Oops: Fatal exception in interrupt <2>[ 399.032320] SMP: stopping secondary CPUs <0>[ 399.033487] Kernel Offset: 0x2244fc200000 from 0xffff800080000000 <0>[ 399.033819] PHYS_OFFSET: 0x40000000 <0>[ 399.034096] CPU features: 0x00000000,68f167a1,ccc6773f <0>[ 399.034779] Memory Limit: none <0>[ 399.035768] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- Links: - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.5/testrun… - https://qa-reports.linaro.org/lkft/linux-mainline-master/build/v6.5/testrun… - https://storage.tuxsuite.com/public/linaro/lkft/builds/2UaRggcJ0lNsDMIbbFai… Steps to reproduce: =================== # # To install tuxrun to your home directory at ~/.local/bin: # pip3 install -U --user tuxrun==0.48.0 # # Or install a deb/rpm depending on the running distribution # See https://tuxmake.org/install-deb/ or # https://tuxmake.org/install-rpm/ # # See https://tuxrun.org/ for complete documentation. # # Please follow the additional instructions if the tests are related to FVP: # https://tuxrun.org/run-fvp/ # tuxrun --runtime podman --device qemu-arm64 --boot-args rw --kernel https://storage.tuxsuite.com/public/linaro/lkft/builds/2UaRggcJ0lNsDMIbbFai… --modules https://storage.tuxsuite.com/public/linaro/lkft/builds/2UaRggcJ0lNsDMIbbFai… --rootfs https://storage.tuxboot.com/debian/bookworm/arm64/rootfs.ext4.xz --parameters SHARD_INDEX=1 --parameters SKIPFILE=skipfile-lkft.yaml --parameters SHARD_NUMBER=5 --parameters KSELFTEST=https://storage.tuxsuite.com/public/linaro/lkft/builds/2UaRggcJ0l… --image docker.io/linaro/tuxrun-dispatcher:v0.48.0 --tests kselftest-net --timeouts boot=30 kselftest-net=30 -- Linaro LKFT https://lkft.linaro.org

1 year, 3 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

Linux-kselftest-mirror August 2023