From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: david@fromorbit.com, linux-btrfs@vger.kernel.org,
fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] generic/304: fix high offset
Date: Wed, 17 Feb 2016 01:56:46 -0800 [thread overview]
Message-ID: <20160217095646.GA21482@infradead.org> (raw)
In-Reply-To: <20160215204614.7977.2848.stgit@birch.djwong.org>
On Mon, Feb 15, 2016 at 12:46:14PM -0800, Darrick J. Wong wrote:
> "Invalid argument" is a better response to an impossibly high offset
> dedupe request than "extents don't match", so change the test.
What does btrfs return here?
next prev parent reply other threads:[~2016-02-17 9:56 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 ` [PATCH 1/3] generic/304: fix high offset Darrick J. Wong
2016-02-17 9:56 ` Christoph Hellwig [this message]
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=20160217095646.GA21482@infradead.org \
--to=hch@infradead.org \
--cc=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).