Google Git
Sign in
chromium/external/github.com/osandov/blktests/bc36cc363930b6ff0d70fd964439d3dd80dd4057
commit
bc36cc363930b6ff0d70fd964439d3dd80dd4057
[log]
author
Shin'ichiro Kawasaki <[email protected]>
Wed Apr 02 07:08:59 2025
committer
Shin'ichiro Kawasaki <[email protected]>
Tue Apr 15 05:41:27 2025
tree
2ec3a3a808a7cf4f47192463ff83c9a0fe76d72a
parent
968026bc4aad4738a8efec19240fdfc0fc06612d [diff]
common/rc,fio: factor out _compare_three_version_numbers()

The helper functions _have_kver() and _have_fio_ver() have the common
logic that compares three numbers with the version string in the format
"a.b.c". Factor out the common logic to the new helper function
_compare_three_version_numbers(). This prepares for to introduce more
functions for version checks.

Signed-off-by: Shin'ichiro Kawasaki <[email protected]>
2 files changed
tree: 2ec3a3a808a7cf4f47192463ff83c9a0fe76d72a
  1. .github/
  2. common/
  3. contrib/
  4. Documentation/
  5. LICENSES/
  6. src/
  7. tests/
  8. .dir-locals.el
  9. .gitignore
  10. check
  11. CONTRIBUTING.md
  12. Makefile
  13. new
  14. README.md
README.md

blktests

Build Status

blktests is a test framework for the Linux kernel block layer and storage stack. It is inspired by the xfstests filesystem testing framework. It was originally written by Omar Sandoval and announced in 2017.

Getting Started

The dependencies are minimal, but make sure you have them installed:

  • bash (>= 4.2)
  • GNU coreutils
  • GNU awk
  • util-linux
  • fio
  • gcc
  • make
  • systemd-udev (udevadm)

Some tests require the following:

  • e2fsprogs, xfsprogs, f2fs-tools and btrfs-progs
  • nvme-cli
  • multipath-tools (Debian, openSUSE, Arch Linux) or device-mapper-multipath (Fedora)
  • nbd-client and nbd-server (Debian) or nbd (Fedora, openSUSE, Arch Linux)
  • dmsetup (Debian) or device-mapper (Fedora, openSUSE, Arch Linux)
  • rublk (cargo install --version=^0.1 rublk) for ublk test
  • python3, ethtool, iproute2 for nvme-tcp zero-copy offload test

Build blktests with make. Optionally, install it to a known location with make install (/usr/local/blktests by default, but this can be changed by passing DESTDIR and/or prefix).

Add the list of block devices you want to test on in a file named config (note: these tests are potentially destructive):

TEST_DEVS=(/dev/nvme0n1 /dev/sdb)

And as root, run the default set of tests with ./check.

Do not add anything to the TEST_DEVS array containing data that you want to keep.

See here for more detailed information on configuration and running tests.

Adding Tests

New test cases are welcomed when,

  • a bug in block layer or storage stack is found and the new test case confirms fix of the bug,
  • a new feature is introduced in block layer or storage stack, and the new test cases confirm that the feature is working well, or,
  • the new test cases extend coverage of block layer and storage stack code.

The ./new script creates a new test from a template. The generated template contains more detailed documentation. The ./new script itself can be referred to as a document. It describes variables and functions that test cases should implement, global variables that test cases can refer and coding guidelines.

Patches to [email protected] and pull requests on GitHub are both accepted. See here for more information on contributing.