From: Shuah Khan <skhan@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: christian@brauner.io, shuah@kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3 1/2] selftests: pidfd: do not use ksft_exit_skip after ksft_set_plan
Date: Tue, 7 Jul 2020 09:24:14 -0600 [thread overview]
Message-ID: <f10aaf26-39f6-79ae-c3cc-56c31835f57e@linuxfoundation.org> (raw)
In-Reply-To: <20200707101936.12052-2-pbonzini@redhat.com>
On 7/7/20 4:19 AM, Paolo Bonzini wrote:
> Calling ksft_exit_skip after ksft_set_plan results in executing fewer tests
> than planned. Use ksft_test_result_skip instead.
>
> The plan passed to ksft_set_plan was wrong, too, so fix it while at it.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Message-Id: <20200623001547.22255-5-pbonzini@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> tools/testing/selftests/pidfd/pidfd_test.c | 34 +++++++++++++++++++---
> 1 file changed, 30 insertions(+), 4 deletions(-)
>
> diff --git a/tools/testing/selftests/pidfd/pidfd_test.c b/tools/testing/selftests/pidfd/pidfd_test.c
> index 7aff2d3b42c0..f65ad4e32353 100644
> --- a/tools/testing/selftests/pidfd/pidfd_test.c
> +++ b/tools/testing/selftests/pidfd/pidfd_test.c
> @@ -8,6 +8,7 @@
> #include <sched.h>
> #include <signal.h>
> #include <stdio.h>
> +#include <stdbool.h>
> #include <stdlib.h>
> #include <string.h>
> #include <syscall.h>
> @@ -27,6 +28,8 @@
>
> #define MAX_EVENTS 5
>
> +static bool have_pidfd_send_signal = false;
You don't need to initialize this to false. Rest looks good.
> +
> static pid_t pidfd_clone(int flags, int *pidfd, int (*fn)(void *))
> {
> size_t stack_size = 1024;
> @@ -56,6 +59,13 @@ static int test_pidfd_send_signal_simple_success(void)
> int pidfd, ret;
> const char *test_name = "pidfd_send_signal send SIGUSR1";
>
> + if (!have_pidfd_send_signal) {
> + ksft_test_result_skip(
> + "%s test: pidfd_send_signal() syscall not supported\n",
> + test_name);
> + return 0;
> + }
> +
> pidfd = open("/proc/self", O_DIRECTORY | O_CLOEXEC);
> if (pidfd < 0)
> ksft_exit_fail_msg(
> @@ -86,6 +96,13 @@ static int test_pidfd_send_signal_exited_fail(void)
> pid_t pid;
> const char *test_name = "pidfd_send_signal signal exited process";
>
> + if (!have_pidfd_send_signal) {
> + ksft_test_result_skip(
> + "%s test: pidfd_send_signal() syscall not supported\n",
> + test_name);
> + return 0;
> + }
> +
> pid = fork();
> if (pid < 0)
> ksft_exit_fail_msg("%s test: Failed to create new process\n",
> @@ -137,6 +154,13 @@ static int test_pidfd_send_signal_recycled_pid_fail(void)
> pid_t pid1;
> const char *test_name = "pidfd_send_signal signal recycled pid";
>
> + if (!have_pidfd_send_signal) {
> + ksft_test_result_skip(
> + "%s test: pidfd_send_signal() syscall not supported\n",
> + test_name);
> + return 0;
> + }
> +
> ret = unshare(CLONE_NEWPID);
> if (ret < 0)
> ksft_exit_fail_msg("%s test: Failed to unshare pid namespace\n",
> @@ -325,15 +349,17 @@ static int test_pidfd_send_signal_syscall_support(void)
>
> ret = sys_pidfd_send_signal(pidfd, 0, NULL, 0);
> if (ret < 0) {
> - if (errno == ENOSYS)
> - ksft_exit_skip(
> + if (errno == ENOSYS) {
> + ksft_test_result_skip(
> "%s test: pidfd_send_signal() syscall not supported\n",
> test_name);
> -
> + return 0;
> + }
> ksft_exit_fail_msg("%s test: Failed to send signal\n",
> test_name);
> }
>
> + have_pidfd_send_signal = true;
> close(pidfd);
> ksft_test_result_pass(
> "%s test: pidfd_send_signal() syscall is supported. Tests can be executed\n",
> @@ -521,7 +547,7 @@ static void test_pidfd_poll_leader_exit(int use_waitpid)
> int main(int argc, char **argv)
> {
> ksft_print_header();
> - ksft_set_plan(4);
> + ksft_set_plan(8);
>
> test_pidfd_poll_exec(0);
> test_pidfd_poll_exec(1);
>
thanks,
-- Shuah
next prev parent reply other threads:[~2020-07-07 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 10:19 [PATCH v3 0/2] selftests: pidfd: prefer ksft_test_result_skip to ksft_exit_* Paolo Bonzini
2020-07-07 10:19 ` [PATCH v3 1/2] selftests: pidfd: do not use ksft_exit_skip after ksft_set_plan Paolo Bonzini
2020-07-07 15:24 ` Shuah Khan [this message]
2020-07-07 10:19 ` [PATCH v3 2/2] selftests: pidfd: skip test if unshare fails with EPERM Paolo Bonzini
2020-07-07 13:52 ` [PATCH v3 0/2] selftests: pidfd: prefer ksft_test_result_skip to ksft_exit_* Christian Brauner
2020-07-07 14:47 ` Shuah Khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f10aaf26-39f6-79ae-c3cc-56c31835f57e@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®