Submitting patches to xfstests based on OSDI '18 paper (CrashMonkey)

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



Hi Ted,

Thanks for encouraging and helping us in the course of building
CrashMonkey for file-system crash consistency testing. Our work is
published in OSDI '18
(https://www.usenix.org/conference/osdi18/presentation/mohan). While
our goal is to enable the integration of a tool like CrashMonkey in
the file-system development cycle, we think it would be beneficial to
add the test suite of about 300 workloads (consisting of 1 core
file-system operation) that we systematically generated, to xfstest.
The complete list of these workloads is in the CrashMonkey repository
(https://github.com/utsaslab/crashmonkey/tree/master/code/tests/seq1).
Given that developers currently use the xfstest, this addition would
ensure that simple crash-consistency bugs are eliminated from any
future kernel versions.

If this idea sounds good to you, we can write a patch for including
our workloads into xfstest, using dm_flakey. If there's some specific
format you want us to follow while writing patches for these
crash-consistency tests, we are happy to adopt it.

Thanks,
Jayashree Mohan



[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