summaryrefslogtreecommitdiffstats
path: root/tools/testing/selftests/seccomp/settings
diff options
context:
space:
mode:
authorThadeu Lima de Souza Cascardo <cascardo@canonical.com>2020-06-01 21:50:12 +0200
committerKees Cook <keescook@chromium.org>2020-07-11 01:01:52 +0200
commitbc32c9c86581abf7baacf71342df3b0affe367db (patch)
treed54044ba404cc7a64e2b50e5e3705e9ef45b310d /tools/testing/selftests/seccomp/settings
parentselftests/seccomp: Expand benchmark to per-filter measurements (diff)
downloadlinux-bc32c9c86581abf7baacf71342df3b0affe367db.tar.xz
linux-bc32c9c86581abf7baacf71342df3b0affe367db.zip
selftests/seccomp: use 90s as timeout
As seccomp_benchmark 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. That is very dependent on the system where it's executed, so may not be observed always, but it has been observed on x86 VMs. Using a 90s timeout seems safe enough. Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@canonical.com> Link: https://lore.kernel.org/r/20200601123202.1183526-1-cascardo@canonical.com Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'tools/testing/selftests/seccomp/settings')
-rw-r--r--tools/testing/selftests/seccomp/settings1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/testing/selftests/seccomp/settings b/tools/testing/selftests/seccomp/settings
new file mode 100644
index 000000000000..ba4d85f74cd6
--- /dev/null
+++ b/tools/testing/selftests/seccomp/settings
@@ -0,0 +1 @@
+timeout=90