linux-kernel - [RFC PATCH v1 9/9] selftest: sync: disable tests that rely on not yet defined behaviour

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed,  9 Mar 2016 12:29:02 -0300
From:	Emilio López <emilio.lopez@...labora.co.uk>
To:	Shuah Khan <shuahkh@....samsung.com>
Cc:	devel@...verdev.osuosl.org,
	Gustavo Padovan <gustavo.padovan@...labora.co.uk>,
	Riley Andrews <riandrews@...roid.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	John Harrison <John.C.Harrison@...el.com>,
	linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
	Greg Hackmann <ghackmann@...gle.com>,
	Rob Clark <robdclark@...il.com>,
	linux-kselftest@...r.kernel.org,
	Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
	Daniel Stone <daniels@...labora.com>,
	Arve Hjønnevåg <arve@...roid.com>,
	Emilio López <emilio.lopez@...labora.co.uk>
Subject: [RFC PATCH v1 9/9] selftest: sync: disable tests that rely on not yet defined behaviour

One of the tests rely on a behaviour only observed on the driver currently
in use in Android. Disable it here until the behaviour is implemented
or it is decided it should not be implemented on the driver in mainline.

Signed-off-by: Emilio López <emilio.lopez@...labora.co.uk>

---

 tools/testing/selftests/sync/sync_test.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/tools/testing/selftests/sync/sync_test.c b/tools/testing/selftests/sync/sync_test.c
index c3e4c01..3f484318 100644
--- a/tools/testing/selftests/sync/sync_test.c
+++ b/tools/testing/selftests/sync/sync_test.c
@@ -66,7 +66,14 @@ int main(void)
 	err += RUN_TEST(test_fence_one_timeline_merge);
 	err += RUN_TEST(test_fence_merge_same_fence);
 	err += RUN_TEST(test_fence_multi_timeline_wait);
+#if 0
+	/* The following test has been disabled due to differences
+	 * between the upstream and Android kernel drivers. The behaviour
+	 * that should occur when destroying a timeline with active fences
+	 * has not been defined yet.
+	 */
 	err += RUN_TEST(test_fence_wait_on_destroyed_timeline);
+#endif
 	err += RUN_TEST(test_stress_two_threads_shared_timeline);
 	err += RUN_TEST(test_consumer_stress_multi_producer_single_consumer);
 	err += RUN_TEST(test_merge_stress_random_merge);
-- 
2.5.0