All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Xiong Zhou <xzhou@redhat.com>
Cc: fstests@vger.kernel.org, ross.zwisler@linux.intel.com,
	dan.j.williams@intel.com
Subject: Re: [PATCH] DAX DIO: DAX mapped area DIO to non-DAX expected failure
Date: Tue, 14 Mar 2017 08:44:03 -0600	[thread overview]
Message-ID: <20170314144403.GA25951@linux.intel.com> (raw)
In-Reply-To: <1489463960-3579-1-git-send-email-xzhou@redhat.com>

On Tue, Mar 14, 2017 at 11:59:20AM +0800, Xiong Zhou wrote:
> It's not supported on raw mode nvdimm, brd ramdisk:
> https://lists.01.org/pipermail/linux-nvdimm/2017-February/008959.html
> 
> It's working on "memory mode" nvdimm, memmap ramdisk.
> 
> Mute output of this subtest to stop the fake failure. Keep this
> routine for sanity check.
> 
> Updating generic/413 and xfs/260.

I don't understand how we can mute the errors that are due to DAX direct I/O
being used in unsupported configurations (raw mode nvdimm, brd ramdisk)
without also muting real errors that happen for supported configs (memory mode
nvidmm)?

It seems like for this test to give us proper coverage, we need to see this
output in all cases, and we just need to document to the user that this test
is expected to fail if you run it against brd or raw mode nvdimms?

Or am I missing something?

- Ross

> Signed-off-by: Xiong Zhou <xzhou@redhat.com>
> ---
>  tests/generic/413 | 6 ++++--
>  tests/xfs/260     | 6 ++++--
>  2 files changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/generic/413 b/tests/generic/413
> index a1cc514..828ef79 100755
> --- a/tests/generic/413
> +++ b/tests/generic/413
> @@ -89,11 +89,13 @@ t_dax_to_nondax()
>  {
>  	prep_files
>  	src/t_mmap_dio $SCRATCH_MNT/tf_s \
> -		$TEST_DIR/tf_d $1 "dio dax to nondax"
> +		$TEST_DIR/tf_d $1 "dio dax to nondax" \
> +		> /dev/null 2>&1
>  
>  	prep_files
>  	src/t_mmap_dio -b $SCRATCH_MNT/tf_s \
> -		$TEST_DIR/tf_d $1 "buffered dax to nondax"
> +		$TEST_DIR/tf_d $1 "buffered dax to nondax" \
> +		> /dev/null 2>&1
>  }
>  
>  t_both_nondax()
> diff --git a/tests/xfs/260 b/tests/xfs/260
> index e613cc0..ff7eed2 100755
> --- a/tests/xfs/260
> +++ b/tests/xfs/260
> @@ -94,13 +94,15 @@ t_dax_to_nondax()
>  	$XFS_IO_PROG -c "chattr +x" $SCRATCH_MNT/tf_s
>  	$XFS_IO_PROG -c "chattr -x" $SCRATCH_MNT/tf_d
>  	src/t_mmap_dio $SCRATCH_MNT/tf_{s,d} \
> -		$1 "dio dax to nondax"
> +		$1 "dio dax to nondax" \
> +		> /dev/null 2>&1
>  
>  	prep_files
>  	$XFS_IO_PROG -c "chattr +x" $SCRATCH_MNT/tf_s
>  	$XFS_IO_PROG -c "chattr -x" $SCRATCH_MNT/tf_d
>  	src/t_mmap_dio -b $SCRATCH_MNT/tf_{s,d} \
> -		$1 "buffered dax to nondax"
> +		$1 "buffered dax to nondax" \
> +		> /dev/null 2>&1
>  }
>  
>  t_both_nondax()
> -- 
> 1.8.3.1
> 

  reply	other threads:[~2017-03-14 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14  3:59 [PATCH] DAX DIO: DAX mapped area DIO to non-DAX expected failure Xiong Zhou
2017-03-14 14:44 ` Ross Zwisler [this message]
2017-03-14 15:07   ` Ross Zwisler
2017-03-15  2:28     ` 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=20170314144403.GA25951@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=fstests@vger.kernel.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 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.