All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
	fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-nvdimm@lists.01.org, dave.jiang@intel.com
Subject: Re: [fstests PATCH 2/2] generic/347: dm-thin lacks DAX support
Date: Thu, 18 Jan 2018 09:06:02 -0700	[thread overview]
Message-ID: <20180118160602.GA21971@linux.intel.com> (raw)
In-Reply-To: <20180118042343.GQ3102@eguan.usersys.redhat.com>

On Thu, Jan 18, 2018 at 12:23:43PM +0800, Eryu Guan wrote:
> On Wed, Jan 17, 2018 at 04:23:51PM -0700, Ross Zwisler wrote:
> > generic/347 currently fails when run in cojunction with the DAX mount
> > option:
> > 
> > generic/347 72s ... - output mismatch (see
> > /root/project/xfstests/results//generic/347.out.bad)
> >     --- tests/generic/347.out	2016-05-12 11:56:32.086618744 -0600
> >     +++ /root/project/xfstests/results//generic/347.out.bad	2018-01-17
> >     16:04:33.459348448 -0700
> >     @@ -1,2 +1,3 @@
> >      QA output created by 347
> >     +mount: /mnt/xfstests_scratch: can't read superblock on
> >     /dev/mapper/thin-vol.
> >      === completed
> >     ...
> >     (Run 'diff -u tests/generic/347.out
> >     /root/project/xfstests/results//generic/347.out.bad'  to see the entire
> >     diff)
> > 
> > This is expected because the dm-thin target currently lacks DAX support.
> > 
> > Just skip this test if we are using DAX.
> > 
> > Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> > ---
> >  tests/generic/347 | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/tests/generic/347 b/tests/generic/347
> > index 3adc6744..0c2dec98 100755
> > --- a/tests/generic/347
> > +++ b/tests/generic/347
> > @@ -72,6 +72,7 @@ _supported_fs generic
> >  _supported_os Linux
> >  _require_scratch_nocheck
> >  _require_dm_target thin-pool
> > +_exclude_scratch_mount_option dax
> 
> IMHO, it'd be better to put this in common/dmthin file, as what's done
> in common/dmerror or common/dmflakey (we grep for dax directly there,
> that's because they've been added before _exclude_scratch_mount_option
> was introduced), so all thinp tests are excluded from dax tests.

Sure, will do.  Thanks for the review.

WARNING: multiple messages have this Message-ID (diff)
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Eryu Guan <eguan@redhat.com>
Cc: linux-ext4@vger.kernel.org, fstests@vger.kernel.org,
	linux-nvdimm@lists.01.org
Subject: Re: [fstests PATCH 2/2] generic/347: dm-thin lacks DAX support
Date: Thu, 18 Jan 2018 09:06:02 -0700	[thread overview]
Message-ID: <20180118160602.GA21971@linux.intel.com> (raw)
In-Reply-To: <20180118042343.GQ3102@eguan.usersys.redhat.com>

On Thu, Jan 18, 2018 at 12:23:43PM +0800, Eryu Guan wrote:
> On Wed, Jan 17, 2018 at 04:23:51PM -0700, Ross Zwisler wrote:
> > generic/347 currently fails when run in cojunction with the DAX mount
> > option:
> > 
> > generic/347 72s ... - output mismatch (see
> > /root/project/xfstests/results//generic/347.out.bad)
> >     --- tests/generic/347.out	2016-05-12 11:56:32.086618744 -0600
> >     +++ /root/project/xfstests/results//generic/347.out.bad	2018-01-17
> >     16:04:33.459348448 -0700
> >     @@ -1,2 +1,3 @@
> >      QA output created by 347
> >     +mount: /mnt/xfstests_scratch: can't read superblock on
> >     /dev/mapper/thin-vol.
> >      === completed
> >     ...
> >     (Run 'diff -u tests/generic/347.out
> >     /root/project/xfstests/results//generic/347.out.bad'  to see the entire
> >     diff)
> > 
> > This is expected because the dm-thin target currently lacks DAX support.
> > 
> > Just skip this test if we are using DAX.
> > 
> > Signed-off-by: Ross Zwisler <ross.zwisler@linux.intel.com>
> > ---
> >  tests/generic/347 | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/tests/generic/347 b/tests/generic/347
> > index 3adc6744..0c2dec98 100755
> > --- a/tests/generic/347
> > +++ b/tests/generic/347
> > @@ -72,6 +72,7 @@ _supported_fs generic
> >  _supported_os Linux
> >  _require_scratch_nocheck
> >  _require_dm_target thin-pool
> > +_exclude_scratch_mount_option dax
> 
> IMHO, it'd be better to put this in common/dmthin file, as what's done
> in common/dmerror or common/dmflakey (we grep for dax directly there,
> that's because they've been added before _exclude_scratch_mount_option
> was introduced), so all thinp tests are excluded from dax tests.

Sure, will do.  Thanks for the review.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  reply	other threads:[~2018-01-18 16:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 23:23 [fstests PATCH 1/2] shared/272: don't use data journaling with DAX Ross Zwisler
2018-01-17 23:23 ` Ross Zwisler
2018-01-17 23:23 ` [fstests PATCH 2/2] generic/347: dm-thin lacks DAX support Ross Zwisler
2018-01-17 23:23   ` Ross Zwisler
2018-01-18  4:23   ` Eryu Guan
2018-01-18  4:23     ` Eryu Guan
2018-01-18  4:23     ` Eryu Guan
2018-01-18 16:06     ` Ross Zwisler [this message]
2018-01-18 16:06       ` Ross Zwisler
2018-01-18 16:07     ` [fstests PATCH v2] " Ross Zwisler
2018-01-18 16:07       ` Ross Zwisler

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=20180118160602.GA21971@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    /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.