Yifei Liu
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Research Interests
Yifei Liu has a total of 5 co-authors. Here are the top co-authors by number of shared publications:
- Erez Zadok
Stony Brook University, Stony Brook, NY, USA
2 shared publications - Geoff Kuenning
Harvey Mudd College, Claremont, CA, USA
2 shared publications - Scott A. Smolka
Computer Science, Stony Brook University
2 shared publications - Gautam Ahuja
Stony Brook University, Stony Brook, New York, USA
1 shared publication - Kamal Parvez
Stony Brook University, Stony Brook, NY, USA
1 shared publication
Latest Publications
- Open Access
- 8 September 2025
- Published by Association for Computing Machinery (ACM)
- p. 151-166
Enhanced File System Testing through Input and Output Coverage
- 8 September 2025
- Published by Association for Computing Machinery (ACM)
- p. 151-166
Open AccessEnhanced File System Testing through Input and Output Coverage
- Open Access
- 9 July 2023
- Published by Association for Computing Machinery (ACM)
- p. 93-101
Input and Output Coverage Needed in File System Testing
File systems need testing to discover bugs and to help ensure reliability. Many file system testing tools are evaluated based on their code coverage. We analyzed recently reported bugs in Ext4 and BtrFS and found a weak correlation between code coverage and test effectiveness: many bugs are missed because they depend on specific inputs, even though the code was covered by a test suite. Our position is that coverage of system call inputs and outputs is critically important for testing file systems. We thus suggest input and output coverage as criteria for file system testing, and show how they can improve the effectiveness of testing. We built a prototype called IOCov to evaluate the input and output coverage of file system testing tools. IOCov identified many untested cases (specific inputs and outputs or ranges thereof) for both CrashMonkey and xfstests. Additionally, we discuss a method and associated metrics to identify over- and under-testing using IOCov.
- 9 July 2023
- Published by Association for Computing Machinery (ACM)
- p. 93-101
Open AccessInput and Output Coverage Needed in File System Testing
File systems need testing to discover bugs and to help ensure reliability. Many file system testing tools are evaluated based on their code coverage. We analyzed recently reported bugs in Ext4 and BtrFS and found a weak correlation between code coverage and test effectiveness: many bugs are missed because they depend on specific inputs, even though the code was covered by a test suite. Our position is that coverage of system call inputs and outputs is critically important for testing file systems. We thus suggest input and output coverage as criteria for file system testing, and show how they can improve the effectiveness of testing. We built a prototype called IOCov to evaluate the input and output coverage of file system testing tools. IOCov identified many untested cases (specific inputs and outputs or ranges thereof) for both CrashMonkey and xfstests. Additionally, we discuss a method and associated metrics to identify over- and under-testing using IOCov.