From: Amir Goldstein <amir73il@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 0/2] xfstests-bld: improve overlayfs testing
Date: Sun, 6 Nov 2016 12:23:15 +0200 [thread overview]
Message-ID: <1478427797-8969-1-git-send-email-amir73il@gmail.com> (raw)
Hi Ted,
Following are the changes to xfstests-bld I have been using to test overlayfs.
xfstests master branch just got updated with several fixes to overlay/* tests.
One overlayfs bug that was caught by generic/375 was fixed for 4.9-rc4 and one
that was caught by generic/157 is queued on overlayfs-next branch.
With these changes to test-appliance, one can test drive overlayfs clone-up
over xfs with reflink support. Xfs with reflink support was merged to 4.9-rc1
and relevant xfsprogs changes are queued on xfsprogs for-next branch.
Overlayfs clone-up is queued on overlayfs-next branch.
Decided to have a little fun and send this one out to you also via github PR.
Thanks for setting up xfstests-bld.
It has been a great help in bringing up my test env.
Amir.
Amir Goldstein (2):
test-appliance: add xfs/reflink config
test-appliance: add support for overlayfs over xfs
.../test-appliance/files/root/fs/overlay/config | 44 ++++++++++++++++++----
.../test-appliance/files/root/fs/xfs/cfg/reflink | 3 ++
kvm-xfstests/util/parse_cli | 2 +-
3 files changed, 40 insertions(+), 9 deletions(-)
create mode 100644 kvm-xfstests/test-appliance/files/root/fs/xfs/cfg/reflink
--
2.7.4
next reply other threads:[~2016-11-06 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 10:23 Amir Goldstein [this message]
2016-11-06 10:23 ` [PATCH 1/2] test-appliance: add xfs/reflink config Amir Goldstein
2016-11-06 10:23 ` [PATCH 2/2] test-appliance: add support for overlayfs over xfs Amir Goldstein
2016-11-07 17:29 ` [PATCH 0/2] xfstests-bld: improve overlayfs testing Theodore Ts'o
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=1478427797-8969-1-git-send-email-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=tytso@mit.edu \
/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).