google / file-system-stress-testing Goto Github PK

A tool that can be used to stress test POSIX filesystems.

License: Apache License 2.0

Makefile 8.03% C 86.58% Shell 5.39%

file-system-stress-testing's Introduction

Summary

A monkey test tool framework that can be used to stress test POSIX filesystems. There is a library of common filesystem operations (open,mmap, etc). And a small framework library that does some housekeeping (like tracking open FDs). Some example tools are provided.

Reading the monkey test overview, would help you understand the goals of this project.

Objectives

Develop a new monkey test tool that will meet these objectives:

Simplify adding new tests to the operational pool.
Increase code sharing of operation pools between different test tools.
Every test tool should use the same execution framework.
Every test tool should have the same command line API.
Every test tool should have a clearly defined test strategy.
Develop methods to reduce the effects of the Pesticide Paradox
Develop methods to reduce the amount of code and the execution time of the monkey test to reproduce the kernel bug.
Develop methods that take advantage of clusters.

Our Approach

Operational Pool

The operation pool is maintained as a library and can be shared between multiple test tools with different test strategies.
Instead of altering an existing operation -- fork the operation and create a new one.

Execution Framework

Use the krt framework for all test tools.
All tools need to have the same command line API to allow script reuse.

Strategy

All test tools use the krt framework and common operation libraries.
Each test tool needs to have a well defined test strategy.
Instead of changing a tool's strategy, fork the tool and create a new one.
Make it easy to add new operations to the pool.
Make it easy to prototype a new test strategy.

Scale

Split the monkey tool into two parts: one tool uses entropy to generate a file system operation list and another tool that replays this pre-generated operation list.

Using pre-generated operation lists is a win due to the future improvements this technique enables:

competitive algorithms can be used to create operation lists that maximize bug count
corpus distillation techniques can be used to create operation lists that maximize code coverage
regression test suites can be created using a set of minimized operation lists that have caused past regressions
improvements can be made to the front end without effecting existing regression tests
automated techniques can be developed to reduce a operation list to the minimum required to reproduce the failure in the software under test

Wiki Page Index

file-system-stress-testing's People

Contributors

Stargazers

Watchers

file-system-stress-testing's Issues

cleanup use of deprecated libarchive function calls

I saw these errors today, when using FreeBSD 10.2

mkpax.c:124:5: warning: 'archive_read_support_compression_all' is deprecated
      [-Wdeprecated-declarations]
    archive_read_support_compression_all(a);
    ^
/usr/include/archive.h:311:15: note: 'archive_read_support_compression_all' declared here
__LA_DECL int archive_read_support_compression_all(struct archive *)
              ^
mkpax.c:125:9: warning: 'archive_read_open_file' is deprecated [-Wdeprecated-declarations]
    if (archive_read_open_file(a, filename, 10240)) {
        ^
/usr/include/archive.h:440:15: note: 'archive_read_open_file' declared here
__LA_DECL int archive_read_open_file(struct archive *,
              ^
mkpax.c:153:5: warning: 'archive_read_finish' is deprecated [-Wdeprecated-declarations]
    archive_read_finish(a);

Security Policy violation Binary Artifacts

This issue was automatically created by Allstar.

Security Policy Violation
Project is out of compliance with Binary Artifacts policy: binaries present in source code

Rule Description
Binary Artifacts are an increased security risk in your repository. Binary artifacts cannot be reviewed, allowing the introduction of possibly obsolete or maliciously subverted executables. For more information see the Security Scorecards Documentation for Binary Artifacts.

Remediation Steps
To remediate, remove the generated executable artifacts from the repository.

Artifacts Found

src/shlib/bsd.lib

Additional Information
This policy is drawn from Security Scorecards, which is a tool that scores a project's adherence to security best practices. You may wish to run a Scorecards scan directly on this repository for more details.

Allstar has been installed on all Google managed GitHub orgs. Policies are gradually being rolled out and enforced by the GOSST and OSPO teams. Learn more at http://go/allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

bstg_fdstore_get2 will not open directories with the default O_RDWR flag

I think there is a bug here:
https://github.com/google/file-system-stress-testing/blob/master/src/lib/fdstore.c#L187

If the target path is a directory, then we will not be able to open it uses O_RDWR.

Any example on how to use this tool

Dear author,

I did not a google and glad to find you have provided such a good staff for the file system testing, however, are there any examples on how to use this tool?

thanks and best regards
Larry Wang