public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Luis Henriques <lhenriques@suse.com>
To: fstests@vger.kernel.org
Cc: Anna Schumaker <Anna.Schumaker@Netapp.com>,
	Luis Henriques <lhenriques@suse.com>
Subject: [PATCH 1/2] generic/430: Fix filename in "copy beyond end" test
Date: Mon, 26 Jun 2017 17:40:52 +0100	[thread overview]
Message-ID: <20170626164053.7634-1-lhenriques@suse.com> (raw)

The cmp command was using the wrong file to perform the comparison.  Use
$testdir/beyond instead of $testdir/end.

Signed-off-by: Luis Henriques <lhenriques@suse.com>
---
 tests/generic/430 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/generic/430 b/tests/generic/430
index 2ec126db9847..5d6b8d6c2aa3 100755
--- a/tests/generic/430
+++ b/tests/generic/430
@@ -87,7 +87,7 @@ md5sum $testdir/{file,end} | _filter_test_dir
 
 echo "Copy beyond end of original file"
 $XFS_IO_PROG -f -c "copy_range -s 4000 -l 2000 $testdir/file" "$testdir/beyond"
-cmp -n 1000 $testdir/file $testdir/end 4000
+cmp -n 1000 $testdir/file $testdir/beyond 4000
 echo "md5sums after copying beyond:"
 md5sum $testdir/{file,beyond} | _filter_test_dir
 

             reply	other threads:[~2017-06-26 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 16:40 Luis Henriques [this message]
2017-06-26 16:40 ` [PATCH 2/2] common/rc: handle xfs_io copy_range when copy_file_range syscall isn't available Luis Henriques
2017-06-27  5:25   ` Eryu Guan
2017-06-27  8:50     ` Luis Henriques
2017-06-28  7:50       ` Eryu Guan
2017-06-28 11:20         ` [PATCH 2/2 v2] " Luis Henriques
2017-06-28 14:21 ` [PATCH 1/2] generic/430: Fix filename in "copy beyond end" test David Disseldorp

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=20170626164053.7634-1-lhenriques@suse.com \
    --to=lhenriques@suse.com \
    --cc=Anna.Schumaker@Netapp.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