Skip to content

Commit 98dc6ad

Browse files
committed
Documentation: describe influence on devices prepared by testing drivers
When blktests runs, it may affect prepared by testing drivers such as null_blk, scsi_debug, loopback and so on. Describe this influence in the documentation. Signed-off-by: Shin'ichiro Kawasaki <[email protected]>
1 parent 7984b8d commit 98dc6ad

File tree

1 file changed

+9
-4
lines changed

1 file changed

+9
-4
lines changed

Documentation/running-tests.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,10 +40,15 @@ overwrite any data on these devices.
4040
TEST_DEVS=(/dev/nvme0n1 /dev/sdb)
4141
```
4242

43-
If `TEST_DEVS` is not defined or is empty, only tests which do not require a
44-
device will be run, which implments the test function 'test()'. If `TEST_DEVS`
45-
is defined as a normal variable instead of an array, it will be converted to an
46-
array by splitting on whitespace.
43+
If `TEST_DEVS` is defined as a normal variable instead of an array, it will be
44+
converted to an array by splitting on whitespace.
45+
46+
If `TEST_DEVS` is undefined or empty, only tests which do not require a device
47+
will be run. These tests, implemented within the 'test()' function, often
48+
prepare test target devices in the function using testing drivers such as
49+
null_blk or scsi_debug. Running these test cases can alter the state of these
50+
devices. If you set up devices using these drivers, their state may be impacted
51+
by the blktests runs.
4752

4853
Some test cases require multiple block devices for single test run. These test
4954
cases implement a special test function test_device_array(). TEST_CASE_DEV_ARRAY

0 commit comments

Comments
 (0)