From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: david@fromorbit.com, darrick.wong@oracle.com
Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
fstests@vger.kernel.org, xfs@oss.sgi.com
Subject: [PATCH v5 00/12] xfstests: minor fixes for the reflink/dedupe tests
Date: Fri, 04 Mar 2016 16:37:18 -0800 [thread overview]
Message-ID: <20160305003717.28738.98818.stgit@birch.djwong.org> (raw)
This is a patch set for xfstests, associated with the fifth revision
to a patch series adding reverse mapping and reflink to XFS. Patches
1, 3-9, and 11 are bug fixes to existing reflink tests.
Patches 2 and 10 add a few more XFS-specific reflink tests to ensure
that we get the CoW and metadata reservation accounting correct.
Patch 12 adds tests for the new block device fallocate call; don't
bother merging it unless the corresponding kernel patches aren't
shouted down after a reasonable amount of time.
Comments and questions are, as always, welcome. The fixes are
available on github[1].
--D
[1] https://github.com/djwong/xfstests/tree/reflink-devel
next reply other threads:[~2016-03-05 0:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 0:37 Darrick J. Wong [this message]
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
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=20160305003717.28738.98818.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=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;
as well as URLs for NNTP newsgroup(s).