selftests: sigaltstack: do not use ksft_exit_skip after ksft_set_plan

Calling ksft_exit_skip after ksft_set_plan results in executing fewer tests
than planned.  Use ksft_test_result_skip when possible, or just bail out if
memory corruption is detected.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

diff --git a/tools/testing/selftests/sigaltstack/sas.c b/tools/testing/selftests/sigaltstack/sas.c
index ad0f8df2ca0af7bccd6a6bd46d36d22480503675..8934a3766d2076bee27a62cd41c6bfa0b3ef4af6 100644 (file)
--- a/tools/testing/selftests/sigaltstack/sas.c
+++ b/tools/testing/selftests/sigaltstack/sas.c
@@ -71,7 +71,7 @@ void my_usr1(int sig, siginfo_t *si, void *u)
        swapcontext(&sc, &uc);
        ksft_print_msg("%s\n", p->msg);
        if (!p->flag) {
-               ksft_exit_skip("[RUN]\tAborting\n");
+               ksft_exit_fail_msg("[RUN]\tAborting\n");
                exit(EXIT_FAILURE);
        }
 }
@@ -144,7 +144,7 @@ int main(void)
        err = sigaltstack(&stk, NULL);
        if (err) {
                if (errno == EINVAL) {
-                       ksft_exit_skip(
+                       ksft_test_result_skip(
                                "[NOTE]\tThe running kernel doesn't support SS_AUTODISARM\n");
                        /*
                         * If test cases for the !SS_AUTODISARM variant were