From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 12/12] block: test fallocate for block devices
Date: Tue, 15 Mar 2016 01:34:37 -0700 [thread overview]
Message-ID: <20160315083437.GB8802@infradead.org> (raw)
In-Reply-To: <20160315034148.GF30721@dastard>
On Tue, Mar 15, 2016 at 02:41:48PM +1100, Dave Chinner wrote:
> I think it's the right place to test it - we have all the
> infrastructure available to do it (i.e. xfs_io and various block
> devices) and we really need to make sure this stuff works,
> especially if we start to write filesystem code that depends on
> correct behaviour...
Ok. But let's keep it outside of the auto group so we don't run purely
block device specific tests every time we do an xfstests run.
next prev parent reply other threads:[~2016-03-15 8:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 0:37 [PATCH v5 00/12] xfstests: minor fixes for the reflink/dedupe tests Darrick J. Wong
2016-03-05 0:37 ` [PATCH 01/12] xfs/207: fix golden output to match FS_IOC_FSSETXATTR hoist Darrick J. Wong
2016-03-05 20:16 ` Christoph Hellwig
2016-03-05 0:37 ` [PATCH 02/12] xfs: test copy-on-write leftover recovery Darrick J. Wong
2016-03-05 20:17 ` Christoph Hellwig
2016-03-05 0:37 ` [PATCH 03/12] reflink: fix fragmentation tests to work on >4k block size filesystems Darrick J. Wong
2016-03-05 20:17 ` Christoph Hellwig
2016-03-05 0:37 ` [PATCH 04/12] xfs/23[3-6]: don't source common/xfs, it doesn't exist Darrick J. Wong
2016-03-05 20:19 ` Christoph Hellwig
2016-03-05 0:37 ` [PATCH 05/12] xfs/206: fix output when mkfs knows about reflink Darrick J. Wong
2016-03-05 20:19 ` Christoph Hellwig
2016-03-05 0:37 ` [PATCH 06/12] xfs/030: fix output on newer filesystems Darrick J. Wong
2016-03-05 20:20 ` Christoph Hellwig
2016-03-23 3:40 ` Dave Chinner
2016-03-05 0:38 ` [PATCH 07/12] xfs/073: fix output Darrick J. Wong
2016-03-05 20:22 ` Christoph Hellwig
2016-03-05 0:38 ` [PATCH 08/12] xfs/122: define _GNU_SOURCE when compiling test program Darrick J. Wong
2016-03-05 20:10 ` Christoph Hellwig
2016-03-05 0:38 ` [PATCH 09/12] xfs/122: support rmapxbt Darrick J. Wong
2016-03-05 20:12 ` Christoph Hellwig
2016-03-05 0:38 ` [PATCH 10/12] xfs: test per-ag allocation accounting during truncate-caused refcountbt expansion Darrick J. Wong
2016-03-05 20:23 ` Christoph Hellwig
2016-03-05 0:38 ` [PATCH 11/12] xfs: remove NOCOW_FL testing from test Darrick J. Wong
2016-03-05 20:10 ` Christoph Hellwig
2016-03-05 0:38 ` [PATCH 12/12] block: test fallocate for block devices Darrick J. Wong
2016-03-05 18:25 ` Christoph Hellwig
2016-03-07 8:26 ` Darrick J. Wong
2016-03-15 3:41 ` Dave Chinner
2016-03-15 8:34 ` Christoph Hellwig [this message]
2016-03-15 19:25 ` [PATCH v2 " Darrick J. Wong
2016-03-05 20:25 ` [PATCH 13/12] xfs/209: filter scratch dir properly Christoph Hellwig
2016-03-06 22:09 ` Darrick J. Wong
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=20160315083437.GB8802@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=linux-ext4@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