On Fri, Dec 13, 2013 at 09:56:57AM +1100, Dave Chinner wrote: > Yes, but that's not the same situation as tmpfs here. A generic > filesystem fits a certain model but the given configuration/kernel > does not necessarily support the feature being tested. Those > features are easily testable by a _requires_* line. > > This case with tmpfs is different - it doesn't support *being > unmounted* during a test because it is volatile. That's a > fundamental change to the assumptions xfstests makes about > filesystems being tested. IOWs, we've got a "generic" filesystem > that is anything but generic. It's not really a fundamental change for tests supposed to be run on the TEST_DIR fs. In fact I'd go so far to say that one patch that unmounts and repairs it manually should switch to the scratch fs. Running the scratch tests on tmpfs is a bit more fragile, but I don't really see a big problem with the concept. > Adding "_requires_non_volatile_fs" to all the generic tests that do > an unmount so that tmpfs can be considered "generic" is just as > painful as modifying the "_supported_fs generic" lines in all the > tests. It just leads us to a game of whack-a-mole. What's the problem? It's not that bad if you look at the series, and as long as someone maintains tmpfs support it shouldn't burden anyone else. If it stops being maintained we can drop the support after a while. Then again we still have utterly bitrotted IRIX support around.. _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
