seccomp_benchmark times out on eoan
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Thadeu Lima de Souza Cascardo | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
seccomp selftests will timeout, causing the test to be detected as failure.
[Fix]
Set timeout to 90s.
[Test case]
Run sudo make run_tests under tools/testing/
[Regression potential]
Minimal, the test could still timeout, but by reading the code, it should take around 42s to 50s to execute in the worst cases, so 90s seem safe enough.
=======
As it tries to calibrate how many samples will take more than 5 seconds to execute, it may end up picking up a number of samples that take 10 (but up to 12) seconds. As the calibration will take double that time, it takes around 20 seconds. Then, it executes the whole thing again, and then once more, with some added overhead. So, the thing might take more than 40 seconds, which is too close to the 45s timeout.
So, it times out once in a while depending on the system. Using a timeout of 90 seconds should be safe enough for this test.
CVE References
Changed in linux (Ubuntu): | |
status: | New → Fix Released |
Changed in linux (Ubuntu Eoan): | |
status: | New → In Progress |
assignee: | nobody → Thadeu Lima de Souza Cascardo (cascardo) |
description: | updated |
Changed in linux (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | Fix Released → In Progress |
Changed in ubuntu-kernel-tests: | |
status: | New → Invalid |
Changed in linux (Ubuntu Eoan): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in ubuntu-kernel-tests: | |
status: | Invalid → Fix Released |
This issue can be found on E-kvm