Linux Test Project
 help / color / mirror / Atom feed
From: "xuyang2018.jy@fujitsu.com" <xuyang2018.jy@fujitsu.com>
To: Li Wang <liwang@redhat.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH] mountns01: wait for umount completed in thread_b
Date: Thu, 7 Jul 2022 10:02:43 +0000	[thread overview]
Message-ID: <62C6BD8E.10802@fujitsu.com> (raw)
In-Reply-To: <20220707093845.946230-1-liwang@redhat.com>

Hi Li

We can also use TST_CHECKPOINT_WAKE_AND_WAIT(0) again,
but use SAFE_WAIT(NULL) is easier.

So
Reviewed-by: Yang Xu <xuyang2018.jy@fujitsu.com>

ps: mountns04 seems doesn't need to use needs_checkpoints member
because we don't use tst_checkpoint* api in there.

Best Regards
Yang Xu
> To get rid of race condition (occurs with umount_folders):
>
>      mountns01.c:42: TPASS: shared mount in parent passed
>      mountns01.c:83: TPASS: shared mount in child passed
>      tst_device.c:394: TWARN: umount('B') failed with EINVAL
>      mountns.h:39: TWARN: umount(B) failed: EINVAL (22)
>
> Signed-off-by: Li Wang<liwang@redhat.com>
> ---
>   testcases/kernel/containers/mountns/mountns01.c | 2 ++
>   testcases/kernel/containers/mountns/mountns02.c | 2 ++
>   testcases/kernel/containers/mountns/mountns03.c | 2 ++
>   3 files changed, 6 insertions(+)
>
> diff --git a/testcases/kernel/containers/mountns/mountns01.c b/testcases/kernel/containers/mountns/mountns01.c
> index 452fe1d10..3e9c22ce3 100644
> --- a/testcases/kernel/containers/mountns/mountns01.c
> +++ b/testcases/kernel/containers/mountns/mountns01.c
> @@ -86,6 +86,8 @@ static void run(void)
>
>   	TST_CHECKPOINT_WAKE(0);
>
> +	SAFE_WAIT(NULL);
> +
>   	SAFE_UMOUNT(DIRA);
>   }
>
> diff --git a/testcases/kernel/containers/mountns/mountns02.c b/testcases/kernel/containers/mountns/mountns02.c
> index cbd435958..4ef1a61b8 100644
> --- a/testcases/kernel/containers/mountns/mountns02.c
> +++ b/testcases/kernel/containers/mountns/mountns02.c
> @@ -87,6 +87,8 @@ static void run(void)
>
>   	TST_CHECKPOINT_WAKE(0);
>
> +	SAFE_WAIT(NULL);
> +
>   	SAFE_UMOUNT(DIRA);
>   }
>
> diff --git a/testcases/kernel/containers/mountns/mountns03.c b/testcases/kernel/containers/mountns/mountns03.c
> index 5c19a96a9..0d8b86f9d 100644
> --- a/testcases/kernel/containers/mountns/mountns03.c
> +++ b/testcases/kernel/containers/mountns/mountns03.c
> @@ -97,6 +97,8 @@ static void run(void)
>
>   	TST_CHECKPOINT_WAKE(0);
>
> +	SAFE_WAIT(NULL);
> +
>   	SAFE_UMOUNT(DIRA);
>   }
>

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

  reply	other threads:[~2022-07-07 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  9:38 [LTP] [PATCH] mountns01: wait for umount completed in thread_b Li Wang
2022-07-07 10:02 ` xuyang2018.jy [this message]
2022-07-08  1:40 ` xuyang2018.jy

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=62C6BD8E.10802@fujitsu.com \
    --to=xuyang2018.jy@fujitsu.com \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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