The particular test that is timing out actually is supposed to emit periodic output to stdout; it basically is running the test program from kernel commit b4a1b4f5047e4f54e194681125c74c0aa64d637d 100000 times and attempts to emit a count every 1000 iterations, writing to and flushing stdout.
The test itself spins up four threads that do keyctl_read() and keyctl_revoke(), to try to trigger a race condition in the kernel.
Is the test timeout a strict timeout, or is it not seeing forward progress via output to stdout?
I know in the kernel autotests stdout gets buffered in some way, so I could adjust the script to emit the counter to stderr instead, if that would help indicate that forward progress is being made.
Hi,
The particular test that is timing out actually is supposed to emit periodic output to stdout; it basically is running the test program from kernel commit b4a1b4f5047e4f5 4e194681125c74c 0aa64d637d 100000 times and attempts to emit a count every 1000 iterations, writing to and flushing stdout.
The test itself spins up four threads that do keyctl_read() and keyctl_revoke(), to try to trigger a race condition in the kernel.
Is the test timeout a strict timeout, or is it not seeing forward progress via output to stdout?
I know in the kernel autotests stdout gets buffered in some way, so I could adjust the script to emit the counter to stderr instead, if that would help indicate that forward progress is being made.