public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Zhao Gongyi <zhaogongyi@huawei.com>
Cc: Matthew Bobrowski <repnop@google.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] syscalls/fanotify07: add stop_children() to cleanup()
Date: Tue, 16 Nov 2021 11:56:50 +0100	[thread overview]
Message-ID: <YZOOcmFmg+2JzK8b@pevik> (raw)
In-Reply-To: <20211105090200.103485-1-zhaogongyi@huawei.com>

Hi all,

> When we run the testcase simultaneously, and the ulimit of open
> files is small, the testcase will fail and remain many while(1)
> tasks in system, it makes the system very stuck.

> Signed-off-by: Zhao Gongyi <zhaogongyi@huawei.com>
> ---
> v1->v2: add stop_children() to cleanup(),suggested by Amir and Matthew.

>  testcases/kernel/syscalls/fanotify/fanotify07.c | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)

> diff --git a/testcases/kernel/syscalls/fanotify/fanotify07.c b/testcases/kernel/syscalls/fanotify/fanotify07.c
> index cc56d9019..40d1b96ce 100644
> --- a/testcases/kernel/syscalls/fanotify/fanotify07.c
> +++ b/testcases/kernel/syscalls/fanotify/fanotify07.c
> @@ -86,15 +86,21 @@ static int stop_children(void)
>  	int child_ret;
>  	int i, ret = 0;

> -	for (i = 0; i < MAX_CHILDREN; i++)
> +	for (i = 0; i < MAX_CHILDREN; i++) {
> +		if (!child_pid[i])
> +			continue;
>  		SAFE_KILL(child_pid[i], SIGKILL);
> +	}

>  	for (i = 0; i < MAX_CHILDREN; i++) {
> +		if (!child_pid[i])
> +			continue;
>  		SAFE_WAITPID(child_pid[i], &child_ret, 0);
>  		if (!WIFSIGNALED(child_ret))
>  			ret = 1;
I slightly prefer instead of using memset code which Amir suggested:
		child_pid[i] = 0;
>  	}

Otherwise LGTM.

Reviewed-by: Petr Vorel <pvorel@suse.cz>

NOTE: patch was corrupted, please take care next time
(error: corrupt patch at line 131)
Also

Kind regards,
Petr

> +	memset(child_pid, 0, sizeof(pid_t) * MAX_CHILDREN);
>  	return ret;
>  }

> @@ -190,6 +196,8 @@ static void setup(void)

>  static void cleanup(void)
>  {
> +	stop_children();
> +
>  	if (fd_notify > 0)
>  		SAFE_CLOSE(fd_notify);
>  }
> @@ -201,6 +209,7 @@ static struct tst_test test = {
>  	.needs_tmpdir = 1,
>  	.forks_child = 1,
>  	.needs_root = 1,
>  };

>  #else

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2021-11-16 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  9:02 [LTP] [PATCH v2] syscalls/fanotify07: add stop_children() to cleanup() Zhao Gongyi
2021-11-16 10:56 ` Petr Vorel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22  8:23 zhaogongyi via ltp

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=YZOOcmFmg+2JzK8b@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=repnop@google.com \
    --cc=zhaogongyi@huawei.com \
    /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