public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, fstests@vger.kernel.org
Subject: Refreshed rootfs.img for kvm-xfstests
Date: Mon, 9 Jan 2017 18:14:50 -0500	[thread overview]
Message-ID: <20170109231450.objek3yirxbtbgzn@thunk.org> (raw)

There is an updated rootfs.img file available at:

    https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests

It includes the latest updates from the xfstests-dev upstream, as well
as updated file system utilities from debian-backports.  It also adds
support for the new encryption teests from Eric Biggers (for this
reason the xfsprogs in this image includes an out-of-tree patch to
allow xfs_io to set the encryption policy).

We also now skip all of the reflink/dedupe tests when running tests
for ext4, to speed up our testing.

This release of kvm-xfstests now supports f2fs (as well as btrfs,
ext2, ext4, overlay, tmpfs, and xfs).

The gce-xfstests driver has been updated to support the latest gcloud
SDK and Debian releases as well as the above changes.  For more
information about this test framework, please see:

    http://thunk.org/gce-xfstests

						- Ted

e2fsprogs	v1.43.3-30-g8df85fb (Sun, 4 Sep 2016 21:32:35 -0400)
fio		fio-2.16 (Mon, 19 Dec 2016 23:12:56 -0700)
quota		2b37958 (Tue, 9 Aug 2016 19:17:56 +0200)
xfsprogs	v4.9.0-1-g07d66eb (Sat, 7 Jan 2017 23:27:26 -0500)
xfstests-bld	39124a6 (Mon, 9 Jan 2017 11:09:14 -0500)
xfstests	linux-v3.8-1306-gbeffdf1 (Sun, 8 Jan 2017 20:30:22 -0500)
						

                 reply	other threads:[~2017-01-09 23:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20170109231450.objek3yirxbtbgzn@thunk.org \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /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