[PATCH 0/8] weekly fstests changes

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]



Hi all,

Here's the usual weekly pile of fstests changes. :)

We start with the same patch as last time that scans kmemleak for leaks
after each test.

Then we move on to a fix in the scrub probe code because upstream
xfsprogs changed xfs_io syntax again.

Third is a patch that adds Unicode linedraw character tests to the two
tests that check that we can store arbitrary byte patterns without
screwing things up.

The fourth patch amends various xfs tests to deal with our slow removal
of zero-alloc transactions, which is causing unexpected fs shutdowns
when free space nears zero.

The fifth patch adds a new test to invoke dm-error on a fsstress run;
this test simulates (for the filesystem) an internal "yank all the disk
cables out" test.

The sixth patch adds FICLONERANGE/FIDEDUPERANGE support to fsstress.
This was helpful in finding a bunch of unhandled corner cases in the xfs
reflink implementation.

Patch seven test write-only fsstress to maximize testing of write paths
where coding mistakes cannot be backed out of so easily.

The final patch in the series fixes the dir/file counts that are
hardcoded in the xfs/068 golden output, since with fsstress doing
reflink now we might get a lot more "files" than we used to.

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



[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux