You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the native_load_attach_detach_unload_random_v4_test from the kernel mode stress test suite causes the test application to hang.
OS information
No response
Steps taken to reproduce bug
Run the kernel mode multi-threaded stress test with the following command line (Note the 1 (one) minute runtime): .\ebpf_stress_tests_km -tt=32 -td=1 -erd=1000 native_load_attach_detach_unload_random_v4_test
Expected behavior
The test should pass successfully and terminate after one minute.
Actual outcome
The test hangs and does not terminate after the specified test duration. While there can be some unavoidable variation in the actual runtime (generally in range of 10 - 30 seconds), the test does not terminate even after 3 minutes.
_While not 100 % reproducible, this failure is very frequent.
The hang is seen in bpf_object__load() in the stack trace of the blocked thread:
Describe the bug
Running the
native_load_attach_detach_unload_random_v4_test
from the kernel mode stress test suite causes the test application to hang.OS information
No response
Steps taken to reproduce bug
Run the kernel mode multi-threaded stress test with the following command line (Note the 1 (one) minute runtime):
.\ebpf_stress_tests_km -tt=32 -td=1 -erd=1000 native_load_attach_detach_unload_random_v4_test
Expected behavior
The test should pass successfully and terminate after one minute.
Actual outcome
The test hangs and does not terminate after the specified test duration. While there can be some unavoidable variation in the actual runtime (generally in range of 10 - 30 seconds), the test does not terminate even after 3 minutes.
_While not 100 % reproducible, this failure is very frequent.
The hang is seen in
bpf_object__load()
in the stack trace of the blocked thread:Additional details
No response
The text was updated successfully, but these errors were encountered: