From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] fstests: generic/260: Make it handle btrfs more gracefully
Date: Thu, 6 Jun 2019 22:44:12 -0700 [thread overview]
Message-ID: <20190607054412.GA15161@infradead.org> (raw)
In-Reply-To: <20190603064009.9891-1-wqu@suse.com>
On Mon, Jun 03, 2019 at 02:40:09PM +0800, Qu Wenruo wrote:
> If a filesystem doesn't map its logical address space (normally the
> bytenr/blocknr returned by fiemap) directly to its devices(s), the
> following assumptions used in the test case is no longer true:
> - trim range start beyond the end of fs should fail
> - trim range start beyond the end of fs with len set should fail
All these assumptions seem generally bogus. I don't think we can just
run this as a generic test.
prev parent reply other threads:[~2019-06-07 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 6:40 [PATCH v2] fstests: generic/260: Make it handle btrfs more gracefully Qu Wenruo
2019-06-05 11:16 ` Nikolay Borisov
2019-06-05 11:53 ` Qu Wenruo
2019-06-05 11:54 ` Nikolay Borisov
2019-06-05 12:05 ` Qu Wenruo
2019-06-07 5:44 ` Christoph Hellwig [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=20190607054412.GA15161@infradead.org \
--to=hch@infradead.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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