937a1c29 - selftests/bpf: skip the timer_lockup test for single-CPU nodes

Thu, 07 Nov 2024 11:52:31 +0000

selftests/bpf: skip the timer_lockup test for single-CPU nodesThe timer_lockup test needs 2 CPUs to work, on single-CPU nodes it failsto set thread affinity to CPU 1 since it doesn't exist: # ./test_progs -t timer_lockup test_timer_lockup:PASS:timer_lockup__open_and_load 0 nsec test_timer_lockup:PASS:pthread_create thread1 0 nsec test_timer_lockup:PASS:pthread_create thread2 0 nsec timer_lockup_thread:PASS:cpu affinity 0 nsec timer_lockup_thread:FAIL:cpu affinity unexpected error: 22 (errno 0) test_timer_lockup:PASS: 0 nsec #406 timer_lockup:FAILSkip the test if only 1 CPU is available.Signed-off-by: Viktor Malik Fixes: 50bd5a0c658d1 ("selftests/bpf: Add timer lockup selftest")Tested-by: Philo Lu Acked-by: Kumar Kartikeya Dwivedi Link: https://lore.kernel.org/r/20241107115231.75200-1-vmalik@redhat.comSigned-off-by: Alexei Starovoitov Signed-off-by: Andrii Nakryiko List of files: /linux-6.15/tools/testing/selftests/bpf/prog_tests/timer_lockup.c

50bd5a0c - selftests/bpf: Add timer lockup selftest

Thu, 11 Jul 2024 05:27:09 +0000

selftests/bpf: Add timer lockup selftestAdd a selftest that tries to trigger a situation where two timer callbacksare attempting to cancel each other's timer. By running them continuously,we hit a condition where both run in parallel and cancel each other.Without the fix in the previous patch, this would cause a lockup ashrtimer_cancel on either side will wait for forward progress from thecallback.Ensure that this situation leads to a EDEADLK error.Signed-off-by: Kumar Kartikeya Dwivedi Signed-off-by: Daniel Borkmann Link: https://lore.kernel.org/bpf/20240711052709.2148616-1-memxor@gmail.com List of files: /linux-6.15/tools/testing/selftests/bpf/prog_tests/timer_lockup.c

Changes in timer_lockup.c

937a1c29 - selftests/bpf: skip the timer_lockup test for single-CPU nodes

50bd5a0c - selftests/bpf: Add timer lockup selftest