All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: guaneryu@gmail.com, fstests@vger.kernel.org, chao@kernel.org
Subject: Re: [PATCH] common/rc: fix to check inode creation on scratch_mnt in _require_btime()
Date: Wed, 24 Oct 2018 15:45:41 +1100	[thread overview]
Message-ID: <20181024044541.GD6311@dastard> (raw)
In-Reply-To: <20181024022645.74084-1-yuchao0@huawei.com>

On Wed, Oct 24, 2018 at 10:26:45AM +0800, Chao Yu wrote:
> _require_btime() should check inode creation feature on SCRATCH_MNT
> mountpoint intead of TEST_DIR mountpoint, otherwise generic/508 will
> fail due to incorrect check of this function.
> 
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> ---
>  common/rc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/common/rc b/common/rc
> index b4987a9cd7f7..5154241a5cee 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -3845,10 +3845,10 @@ _dmsetup_create()
>  
>  _require_btime()
>  {
> -	$XFS_IO_PROG -f $TEST_DIR/test_creation_time -c "statx -v" \
> +	$XFS_IO_PROG -f $SCRATCH_MNT/test_creation_time -c "statx -v" \
>  		| grep btime >>$seqres.full 2>&1 || \
>  		_notrun "inode creation time not supported by this filesystem"
> -	rm -f $TEST_DIR/test_creation_time
> +	rm -f $SCRATCH_MNT/test_creation_time
>  }

This doesn't work. the scratch device is not mounted at the time
generic/508 calls it.

If you are going to check the scratch device, the function needs to
be called _require_scratch_btime and be called after
scratch_mkfs/scratch_mount has been run by the test.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2018-10-24 13:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  2:26 [PATCH] common/rc: fix to check inode creation on scratch_mnt in _require_btime() Chao Yu
2018-10-24  4:45 ` Dave Chinner [this message]
2018-10-24  7:25   ` Chao Yu

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=20181024044541.GD6311@dastard \
    --to=david@fromorbit.com \
    --cc=chao@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=guaneryu@gmail.com \
    --cc=yuchao0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.