linux-ext4 - Refreshed rootfs.img for kvm-xfstests

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160630152816.GA2784@thunk.org>
Date:	Thu, 30 Jun 2016 11:28:16 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	linux-ext4@...r.kernel.org
Subject: Refreshed rootfs.img for kvm-xfstests

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.  This
image also includes the dbench binary which enables generic/241.
There is also support for testing the virtio-rng kernel driver (not
for file system testing).

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

    http://thunk.org/gce-xfstests

Finally, it is now possible to build tar.gz file with all of the
xfstests-bld test runner infrastructure using "./gen-image
--out-tar=rootfs.tar.gz".  This can be used for those people who want
to run xfstests on bare hardware without using KVM.  This also allows
xfstests-bld to be built on a Debian armhf build server, and then
create a tar.gz file that can be used to run a chroot environment on
an Android device.  (This requires using an external drive attached to
a USB C hub, with a special kernel which forces SELinux in Permissive
mode.  More documentation and automation will hopefully follow.)

Cheers,

						- Ted


--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html