public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: yangx.jy@cn.fujitsu.com
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH v2] generic/446: make sure all background processes are dead before umount
Date: Thu, 27 Jul 2017 13:22:10 +0800	[thread overview]
Message-ID: <20170727052210.GB9167@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170725080421.15306-1-eguan@redhat.com>

Hi Xiao Yang,

On Tue, Jul 25, 2017 at 04:04:21PM +0800, Eryu Guan wrote:
> The $dread_pid refers to the while-true-do loop, wait for $dread_pid
> doesn't mean the xfs_io direct read process is already dead,
> sometimes xfs_io process is still running and blocking
> _scratch_unmount.
> 
> Fix it by making the direct read does a fixed number of loop and
> break out the second mmap-fpunch loop if the first loop exits. At
> this point we're sure that there's no unfinished background process
> blocking the umount.
> 
> Signed-off-by: Eryu Guan <eguan@redhat.com>
> ---
> v2:
> - move 'kill' to while loop condition to simplify the second loop
> - add more comments about when to exit the loop

Would you please help test & review and provide reviewed-by tag if you
think it's OK? Thanks a lot!

Eryu

> 
>  tests/generic/446 | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tests/generic/446 b/tests/generic/446
> index 62ae449de6b1..6a1b69aa2edc 100755
> --- a/tests/generic/446
> +++ b/tests/generic/446
> @@ -61,20 +61,20 @@ filesz=$((65536 * 2))
>  $XFS_IO_PROG -f -c "truncate $((filesz * 2))" $SCRATCH_MNT/file >> $seqres.full
>  
>  # run a background dio read to a hole in a loop
> -while true; do
> +for i in `seq 0 999`; do
>  	$XFS_IO_PROG -d -c "pread 0 $filesz" $SCRATCH_MNT/file > /dev/null 2>&1
>  done &
>  
>  dread_pid=$!
>  
>  # run mapped write to the same hole as dio read
> -for i in `seq 0 999`; do
> +# loop until background dio read exits
> +while kill -s 0 $dread_pid >/dev/null 2>&1; do
>  	$XFS_IO_PROG -c "mmap 0 $filesz" -c "mwrite 0 $filesz" $SCRATCH_MNT/file \
>  		> /dev/null
>  	$XFS_IO_PROG -c "fpunch 0 $filesz" $SCRATCH_MNT/file > /dev/null
>  done
>  
> -kill -9 $dread_pid > /dev/null 2>&1
>  wait $dread_pid > /dev/null 2>&1
>  
>  echo "Silence is golden"
> -- 
> 2.13.3
> 

  reply	other threads:[~2017-07-27  5:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 10:11 [PATCH] generic/446: make sure all background processes are dead before umount Eryu Guan
2017-07-25  1:39 ` Xiao Yang
2017-07-25  6:31   ` Eryu Guan
2017-07-25  7:43     ` Xiao Yang
2017-07-25  7:50       ` Eryu Guan
2017-07-25  8:04 ` [PATCH v2] " Eryu Guan
2017-07-27  5:22   ` Eryu Guan [this message]
2017-07-27  6:30     ` Xiao Yang

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=20170727052210.GB9167@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=yangx.jy@cn.fujitsu.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