public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Xiong Zhou <xzhou@redhat.com>
Cc: fstests@vger.kernel.org, linux-nvdimm@ml01.01.org
Subject: Re: [PATCH 1/4] common/rc: add _require_scratch_dax
Date: Thu, 19 Jan 2017 12:17:00 +0800	[thread overview]
Message-ID: <20170119041700.GR1859@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1484708826-23529-2-git-send-email-xzhou@redhat.com>

On Wed, Jan 18, 2017 at 11:07:03AM +0800, Xiong Zhou wrote:
> To make sure we can test DAX feature on SCRATCH_DEV.
> 
> Signed-off-by: Xiong Zhou <xzhou@redhat.com>
> ---
>  common/rc | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/common/rc b/common/rc
> index 892c46e..ea7956b 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -2632,6 +2632,16 @@ _require_scratch_shutdown()
>  	_scratch_unmount
>  }
>  
> +# Does dax mount option work on this dev/fs?
> +_require_scratch_dax()
> +{
> +	_scratch_unmount

Use _require_scratch instead of _scratch_unmount here. _require_scratch
ensures we have SCRATCH_DEV defined and unmounts it if it's mounted.

Thanks,
Eryu

> +	_scratch_mkfs > /dev/null 2>&1
> +	_scratch_mount -o dax || \
> +		_notrun "$SCRATCH_DEV $FSTYP does not support -o dax"
> +	_scratch_unmount
> +}
> +
>  # Does norecovery support by this fs?
>  _require_norecovery()
>  {
> -- 
> 1.8.3.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-01-19  4:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18  3:07 [PATCH 0/4] mmap dio and DAX Xiong Zhou
2017-01-18  3:07 ` [PATCH 1/4] common/rc: add _require_scratch_dax Xiong Zhou
2017-01-19  4:17   ` Eryu Guan [this message]
2017-01-18  3:07 ` [PATCH 2/4] src/t_mmap_dio: add mmap dio test Xiong Zhou
2017-01-18  3:07 ` [PATCH 3/4] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-01-19  4:24   ` Eryu Guan
2017-01-18  3:07 ` [PATCH 4/4] generic: test mmap dio through DAX and non-DAX Xiong Zhou
2017-01-19  5:54   ` Eryu Guan
2017-01-19 10:13     ` [PATCH v2 0/2] mmap dio and DAX Xiong Zhou
2017-01-19 10:13       ` [PATCH v2 1/2] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-01-19 20:49         ` Ross Zwisler
2017-01-20  1:15           ` Xiong Zhou
2017-01-20  2:21           ` [PATCH v3] " Xiong Zhou
2017-01-20  6:15             ` [PATCH v4 0/2] mmap dio and DAX Xiong Zhou
2017-01-20  6:15               ` [PATCH v4 1/2] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-02-04 15:17                 ` [PATCH] fixup! " Ross Zwisler
2017-02-05  6:21                   ` [PATCH v5 0/2] mmap dio and DAX Xiong Zhou
2017-02-05  6:21                     ` [PATCH v5 1/2] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-02-06 19:13                       ` Ross Zwisler
2017-02-05  6:21                     ` [PATCH v5 2/2] generic: test mmap io through DAX and non-DAX Xiong Zhou
2017-02-06 19:17                       ` Ross Zwisler
2017-02-08  4:11                         ` [PATCH v6 0/2] mmap dio and DAX Xiong Zhou
2017-02-08  4:11                           ` [PATCH v6 1/2] xfs: test per-inode DAX flag by IO Xiong Zhou
2017-02-08  4:11                           ` [PATCH v6 2/2] generic: test mmap io through DAX and non-DAX Xiong Zhou
2017-02-17  6:46                             ` Eryu Guan
2017-02-17  6:52                               ` Xiong Zhou
2017-01-20  6:15               ` [PATCH v4 " Xiong Zhou
2017-01-24 22:28               ` [PATCH v4 0/2] mmap dio and DAX Ross Zwisler
2017-02-03  5:57                 ` Xiong Zhou
2017-02-03  6:29                   ` Eryu Guan
2017-02-03 16:57                   ` Ross Zwisler
2017-02-04 10:14                     ` Xiong Zhou
2017-01-19 10:13       ` [PATCH v2 2/2] generic: test mmap dio through DAX and non-DAX Xiong Zhou

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=20170119041700.GR1859@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-nvdimm@ml01.01.org \
    --cc=xzhou@redhat.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