Google Git
Sign in
chromium/external/github.com/osandov/blktests/3ca2657f94b8923178d22db186334d51743118d2
commit
3ca2657f94b8923178d22db186334d51743118d2
[log]
author
Bart Van Assche <bvanassche@acm.org>
Thu Jul 27 23:37:43 2023
committer
Bart Van Assche <bvanassche@acm.org>
Tue Dec 10 22:41:53 2024
tree
2a7d1f629821b093ceecbdb9c766b57c56874e6c
parent
546ded77c1a7db3d7cd65adce4f3798724218fba [diff]
zbd/012: Test requeuing of zoned writes and queue freezing

Test concurrent requeuing of zoned writes and request queue freezing. While
this test passes with kernel 6.9, it triggers a hang with kernels 6.10..6.12.
This shows that this hang is a regression introduced by the zone write
plugging code.

sysrq: Show Blocked State
task:(udev-worker)   state:D stack:0     pid:75392 tgid:75392 ppid:2178   flags:0x00000006
Call Trace:
 <TASK>
 __schedule+0x3e8/0x1410
 schedule+0x27/0xf0
 blk_mq_freeze_queue_wait+0x6f/0xa0
 queue_attr_store+0x60/0xc0
 kernfs_fop_write_iter+0x13e/0x1f0
 vfs_write+0x25b/0x420
 ksys_write+0x65/0xe0
 do_syscall_64+0x82/0x160
 entry_SYSCALL_64_after_hwframe+0x76/0x7e

Signed-off-by: Bart Van Assche <bvanassche@acm.org>
2 files changed
tree: 2a7d1f629821b093ceecbdb9c766b57c56874e6c
  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 linux-block@vger.kernel.org and pull requests on GitHub are both accepted. See here for more information on contributing.