From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>,
"christian@brauner.io" <christian@brauner.io>,
"shuah@kernel.org" <shuah@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
Philip Li <philip.li@intel.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2] ksefltest: pidfd: Fix wait_states: Test terminated by timeout
Date: Thu, 13 Jan 2022 05:51:31 +0000 [thread overview]
Message-ID: <d8961bd4-d2fd-6db3-345c-1ad930d03e3f@fujitsu.com> (raw)
In-Reply-To: <20211217093040.9530-1-lizhijian@cn.fujitsu.com>
ping
On 17/12/2021 17:30, Li Zhijian wrote:
> 0Day/LKP observed that the kselftest blocks foever since one of the
> pidfd_wait doesn't terminate in 1 of 30 runs. After digging into
> the source, we found that it blocks at:
> ASSERT_EQ(sys_waitid(P_PIDFD, pidfd, &info, WCONTINUED, NULL), 0);
>
> we can reproduce it by:
> $ while true; do make run_tests -C pidfd; done
>
> Introduce a blocking read in child process to make sure the parent can
> check its WCONTINUED.
>
> CC: Philip Li <philip.li@intel.com>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
> ---
> V2: rewrite with pipe to avoid usleep
> ---
> tools/testing/selftests/pidfd/pidfd_wait.c | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/pidfd/pidfd_wait.c b/tools/testing/selftests/pidfd/pidfd_wait.c
> index be2943f072f6..d5c0ffa26c32 100644
> --- a/tools/testing/selftests/pidfd/pidfd_wait.c
> +++ b/tools/testing/selftests/pidfd/pidfd_wait.c
> @@ -96,21 +96,26 @@ TEST(wait_states)
> .flags = CLONE_PIDFD | CLONE_PARENT_SETTID,
> .exit_signal = SIGCHLD,
> };
> - int ret;
> + int ret, pfd[2];
> pid_t pid;
> siginfo_t info = {
> .si_signo = 0,
> };
> -
> + ASSERT_EQ(pipe(pfd), 0);
> pid = sys_clone3(&args);
> ASSERT_GE(pid, 0);
>
> if (pid == 0) {
> + char buf[2];
> + close(pfd[1]);
> kill(getpid(), SIGSTOP);
> + ASSERT_EQ(read(pfd[0], buf, 1), 1);
> + close(pfd[0]);
> kill(getpid(), SIGSTOP);
> exit(EXIT_SUCCESS);
> }
>
> + close(pfd[0]);
> ASSERT_EQ(sys_waitid(P_PIDFD, pidfd, &info, WSTOPPED, NULL), 0);
> ASSERT_EQ(info.si_signo, SIGCHLD);
> ASSERT_EQ(info.si_code, CLD_STOPPED);
> @@ -119,6 +124,8 @@ TEST(wait_states)
> ASSERT_EQ(sys_pidfd_send_signal(pidfd, SIGCONT, NULL, 0), 0);
>
> ASSERT_EQ(sys_waitid(P_PIDFD, pidfd, &info, WCONTINUED, NULL), 0);
> + ASSERT_EQ(write(pfd[1], "C", 1), 1);
> + close(pfd[1]);
> ASSERT_EQ(info.si_signo, SIGCHLD);
> ASSERT_EQ(info.si_code, CLD_CONTINUED);
> ASSERT_EQ(info.si_pid, parent_tid);
prev parent reply other threads:[~2022-01-13 5:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 9:30 Li Zhijian
2022-01-13 5:51 ` lizhijian [this message]
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=d8961bd4-d2fd-6db3-345c-1ad930d03e3f@fujitsu.com \
--to=lizhijian@fujitsu.com \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=philip.li@intel.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®