From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: Block btrfs from test case generic/372
Date: Tue, 15 Nov 2016 00:57:41 -0800 [thread overview]
Message-ID: <20161115085741.GA25495@infradead.org> (raw)
In-Reply-To: <20161115081410.6779-1-quwenruo@cn.fujitsu.com>
On Tue, Nov 15, 2016 at 04:14:10PM +0800, Qu Wenruo wrote:
> Since btrfs always return the whole extent even part of it is shared
> with other files, so the hole/extent counts differs for "file1" in this
> test case.
This would need an extremly detailed comment in the test case on why
btrfs is skipped IFF we decide to apply it. That being siad I think
reporing shared extents incorrectly is a bug independent of how they
are implemented internally.
next prev parent reply other threads:[~2016-11-15 8:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 8:14 [PATCH] fstests: Block btrfs from test case generic/372 Qu Wenruo
2016-11-15 8:57 ` Christoph Hellwig [this message]
2016-11-15 9:15 ` Qu Wenruo
[not found] <20161115081332.6432-1-quwenruo@cn.fujitsu.com>
2016-11-16 21:12 ` Dave Chinner
2016-11-17 1:13 ` Qu Wenruo
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=20161115085741.GA25495@infradead.org \
--to=hch@infradead.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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.