Remove STD_FUNCTIONAL_TEST
Only small part of the testcases was using STD_FUNCTIONAL_TEST and these
that were actually using it mostly misused the interface or used it only
to disable the tst_rest(TPASS, "sycall passed") message.
The default value was STD_FUNCTION_TEST enabled, so this only removes
code that is not executed in LTP testrun and there should be no
functional changes.
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
diff --git a/testcases/kernel/syscalls/munmap/munmap01.c b/testcases/kernel/syscalls/munmap/munmap01.c
index 6f4fc11..67f9dae 100644
--- a/testcases/kernel/syscalls/munmap/munmap01.c
+++ b/testcases/kernel/syscalls/munmap/munmap01.c
@@ -124,24 +124,16 @@
tst_resm(TPASS, "call succedded");
#else
/*
- * Perform functional verification if test
- * executed without (-f) option.
+ * Check whether further reference is possible
+ * to the unmapped memory region by writing
+ * to the first byte of region with
+ * some arbitrary number.
*/
- if (STD_FUNCTIONAL_TEST) {
- /*
- * Check whether further reference is possible
- * to the unmapped memory region by writing
- * to the first byte of region with
- * some arbitrary number.
- */
- *addr = 50;
+ *addr = 50;
- /* This message is printed if no SIGSEGV */
- tst_resm(TFAIL, "process succeeds to refer unmapped "
- "memory region");
- } else {
- tst_resm(TPASS, "call succeeded");
- }
+ /* This message is printed if no SIGSEGV */
+ tst_resm(TFAIL, "process succeeds to refer unmapped "
+ "memory region");
#endif
cleanup();