public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Brian Foster <bfoster@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] fsx: test copy_file_range() using non-zero length copy
Date: Wed, 10 Apr 2019 08:13:52 -0700	[thread overview]
Message-ID: <20190410151352.GH32415@magnolia> (raw)
In-Reply-To: <20190410111359.5243-1-bfoster@redhat.com>

On Wed, Apr 10, 2019 at 07:13:59AM -0400, Brian Foster wrote:
> The copy_file_range() test detection code performs a zero-length
> copy to determine whether to perform such calls during the test run.
> While this detects the common case of syscall availability,
> copy_file_range() has a somewhat variable implementation on the
> kernel side that can depend on certain per-filesystem features, etc.
> In some implementations, a zero length copy can shortcut and return
> success before ever invoking per-filesystem functionality and thus
> not thoroughly testing the copy mechanism on the current system.
> This can cause the test detection code to pass only to run into an
> immediate failure on the first copy_file_range() call during the
> test.
> 
> Tweak test_copy_range() to perform a small single byte copy to avoid
> this problem. Also fix a typo bug in the errno check of the clone
> range detection logic.
> 
> Signed-off-by: Brian Foster <bfoster@redhat.com>

Looks ok,
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>

--D

> ---
>  ltp/fsx.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/ltp/fsx.c b/ltp/fsx.c
> index 391824bf..06d08e4e 100644
> --- a/ltp/fsx.c
> +++ b/ltp/fsx.c
> @@ -1364,7 +1364,7 @@ test_clone_range(void)
>  	};
>  
>  	if (ioctl(fd, FICLONERANGE, &fcr) &&
> -	    (errno = EOPNOTSUPP || errno == ENOTTY)) {
> +	    (errno == EOPNOTSUPP || errno == ENOTTY)) {
>  		if (!quiet)
>  			fprintf(stderr,
>  				"main: filesystem does not support "
> @@ -1581,9 +1581,9 @@ do_dedupe_range(unsigned offset, unsigned length, unsigned dest)
>  int
>  test_copy_range(void)
>  {
> -	loff_t o1 = 0, o2 = 0;
> +	loff_t o1 = 0, o2 = 1;
>  
> -	if (syscall(__NR_copy_file_range, fd, &o1, fd, &o2, 0, 0) == -1 &&
> +	if (syscall(__NR_copy_file_range, fd, &o1, fd, &o2, 1, 0) == -1 &&
>  	    (errno == ENOSYS || errno == EOPNOTSUPP || errno == ENOTTY)) {
>  		if (!quiet)
>  			fprintf(stderr,
> -- 
> 2.17.2
> 

      reply	other threads:[~2019-04-10 15:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 11:13 [PATCH] fsx: test copy_file_range() using non-zero length copy Brian Foster
2019-04-10 15:13 ` Darrick J. Wong [this message]

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=20190410151352.GH32415@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=bfoster@redhat.com \
    --cc=fstests@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox