linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: david@fromorbit.com, darrick.wong@oracle.com
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: [PATCH 1/3] generic/304: fix high offset
Date: Mon, 15 Feb 2016 12:46:14 -0800	[thread overview]
Message-ID: <20160215204614.7977.2848.stgit@birch.djwong.org> (raw)
In-Reply-To: <20160215204608.7977.2802.stgit@birch.djwong.org>

"Invalid argument" is a better response to an impossibly high offset
dedupe request than "extents don't match", so change the test.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
---
 tests/generic/304.out |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


diff --git a/tests/generic/304.out b/tests/generic/304.out
index 4af2a39..7b5ff0e 100644
--- a/tests/generic/304.out
+++ b/tests/generic/304.out
@@ -8,7 +8,7 @@ dedupe: Invalid argument
 Dedupe past maximum file size in dest file (should fail)
 dedupe: Invalid argument
 Dedupe high offset to low offset
-dedupe: Extents did not match.
+dedupe: Invalid argument
 Dedupe past source file EOF (should fail)
 dedupe: Invalid argument
 Dedupe max size at nonzero offset (should fail)


  reply	other threads:[~2016-02-15 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 20:46 [PATCH v4.3 0/3] xfstests: minor fixes for the reflink/dedupe tests Darrick J. Wong
2016-02-15 20:46 ` Darrick J. Wong [this message]
2016-02-17  9:56   ` [PATCH 1/3] generic/304: fix high offset Christoph Hellwig
2016-02-17 10:04     ` Filipe Manana
2016-02-17 10:10       ` Christoph Hellwig
2016-02-15 20:46 ` [PATCH 2/3] punch-alternating: use the block size reported by the fs for punching Darrick J. Wong
2016-02-17  9:57   ` Christoph Hellwig
2016-02-15 20:46 ` [PATCH 3/3] xfs/24[356]: check for -c switch to xfs_io bmap command Darrick J. Wong
2016-02-17  9:58   ` Christoph Hellwig

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=20160215204614.7977.2848.stgit@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).