| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20240220000802.162556-1-sj@kernel.org>
Date: Mon, 19 Feb 2024 16:08:02 -0800
From: SeongJae Park <sj@...nel.org>
To: shuah@...nel.org
Cc: ryan.roberts@....com,
abuehaze@...zon.com,
brauner@...nel.org,
jlayton@...nel.org,
jack@...e.cz,
keescook@...omium.org,
linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org,
stable@...r.kernel.org,
Vijaikumar_Kanagarajan@...tor.com,
SeongJae Park <sj@...nel.org>
Subject: [PATCH v3] selftests/mqueue: Set timeout to 180 seconds
While mq_perf_tests runs with the default kselftest timeout limit, which
is 45 seconds, the test takes about 60 seconds to complete on i3.metal
AWS instances. Hence, the test always times out. Increase the timeout
to 180 seconds.
Fixes: 852c8cbf34d3 ("selftests/kselftest/runner.sh: Add 45 second timeout per test")
Cc: <stable@...r.kernel.org> # 5.4.x
Signed-off-by: SeongJae Park <sj@...nel.org>
Reviewed-by: Kees Cook <keescook@...omium.org>
---
Changes from v2
(https://lore.kernel.org/r/20240220000243.162285-1-sj@kernel.org)
- Update commit message about the new timeout limit to 180 seconds
- Remove wrong Link: line
Changes from v1
(https://lore.kernel.org/r/20240208212925.68286-1-sj@kernel.org)
- Use 180 seconds timeout instead of 100 seconds
tools/testing/selftests/mqueue/setting | 1 +
1 file changed, 1 insertion(+)
create mode 100644 tools/testing/selftests/mqueue/setting
diff --git a/tools/testing/selftests/mqueue/setting b/tools/testing/selftests/mqueue/setting
new file mode 100644
index 000000000000..a953c96aa16e
--- /dev/null
+++ b/tools/testing/selftests/mqueue/setting
@@ -0,0 +1 @@
+timeout=180
--
2.39.2
Powered by blists - more mailing lists