Commit 5b0b77ac authored by Paolo Bonzini's avatar Paolo Bonzini Committed by Shuah Khan
Browse files

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: default avatarPaolo Bonzini <pbonzini@redhat.com>
Signed-off-by: default avatarShuah Khan <skhan@linuxfoundation.org>
parent f000a39c

tools/testing/selftests/sigaltstack/sas.c

+2 −2
Original line number Diff line number Diff line
@@ -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

CRA Git | Maintained and supported by SUSTech CRA and CCSE