mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Christian Brauner <christian.brauner@ubuntu.com>,
	"lizhijian@fujitsu.com" <lizhijian@fujitsu.com>
Cc: "linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Christian Brauner <christian@brauner.io>,
	Philip Li <philip.li@intel.com>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 2/2] ksefltest: pidfd: Fix wait_states: Test terminated by timeout
Date: Mon, 6 Dec 2021 06:01:59 +0000	[thread overview]
Message-ID: <31037d09-a42b-3226-d447-9729cc472a2e@fujitsu.com> (raw)
In-Reply-To: <e5567974-42ba-0864-4340-c435db6ad0c1@linuxfoundation.org>



On 04/12/2021 01:03, Shuah Khan wrote:
> On 10/29/21 2:32 AM, Christian Brauner wrote:
>> On Fri, Oct 29, 2021 at 10:45:28AM +0800, 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
>>>
>>> a delay to ensure that the parent can see child process WCONTINUED.
>>>
>>> CC: Christian Brauner <christian@brauner.io>
>>> CC: Shuah Khan <shuah@kernel.org>
>>> CC: Philip Li <philip.li@intel.com>
>>> Reported-by: kernel test robot <lkp@intel.com>
>>> Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com>
>>> ---
>>
>> Not a fan of the usleep() solution but if it fixes it it's fine for
>> a test, I think.
>> Acked-by: Christian Brauner <christian.brauner@ubuntu.com>
>>
>
> I don't like introducing usleep() which will increase the kselftest
> run-time. Every little bit adds up if we allow usleep() in tests.

Thanks for your comments.

how about introduce a pipe to communicate between child and parent.


 From d68c4629dd60a1e22cb83b771d38e899352ff9a9 Mon Sep 17 00:00:00 2001
From: Li Zhijian <lizhijian@cn.fujitsu.com>
Date: Tue, 26 Oct 2021 16:39:56 +0800
Subject: [PATCH] ksefltest: pidfd: Fix wait_states: Test terminated by timeout

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>
---
  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);
-- 
2.33.0

  reply	other threads:[~2021-12-06  6:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  2:45 [PATCH 1/2] kselftest: signal all child processes Li Zhijian
2021-10-29  2:45 ` [PATCH 2/2] ksefltest: pidfd: Fix wait_states: Test terminated by timeout Li Zhijian
2021-10-29  8:32   ` Christian Brauner
2021-12-03 17:03     ` Shuah Khan
2021-12-06  6:01       ` lizhijian [this message]
2021-10-29  8:31 ` [PATCH 1/2] kselftest: signal all child processes Christian Brauner
2021-10-29  8:41   ` lizhijian
2021-12-03  3:05   ` lizhijian
2021-12-03 17:03     ` Shuah Khan
2021-12-17  9:35       ` lizhijian

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=31037d09-a42b-3226-d447-9729cc472a2e@fujitsu.com \
    --to=lizhijian@fujitsu.com \
    --cc=christian.brauner@ubuntu.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 \
    --cc=skhan@linuxfoundation.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®