generic/484: add _require_xfs_io_command "syncfs"

[xfstests-dev.git] / README

diff --git a/README b/README
index 73f057f3d403fd9a78fd7d08bfb82973eb95e2a4..094a77422ea1c7a50928c59925da1e7a4ea65ed2 100644 (file)
--- a/README
+++ b/README
@@ -19,7 +19,7 @@ _______________________
        (Note that for RHEL and CentOS, you may need the EPEL repo.)
 - run make
 - run make install
-- create fsgqa test user ("sudo useradd fsgqa")
+- create fsgqa test user ("sudo useradd -m fsgqa")
 - create fsgqa group ("sudo groupadd fsgqa")
 - create 123456-fsgqa test user ("sudo useradd 123456-fsgqa")
 
@@ -33,7 +33,7 @@ Preparing system for tests:
     - install administrative tools specific to the filesystem you wish to test
     - If you wish to run the udf components of the suite install
       mkudffs. Also download and build the Philips UDF Verification Software
-      from http://www.extra.research.philips.com/udf/, then copy the udf_test
+      from https://www.lscdweb.com/registered/udf_verifier.html, then copy the udf_test
       binary to xfstests/src/. If you wish to disable UDF verification test
       set the environment variable DISABLE_UDF_TEST to 1.
 
@@ -99,6 +99,9 @@ Preparing system for tests:
                that relevant results are compared.  For example 'spinningrust'
                for configurations that use spinning disks and 'nvme' for tests
                using nvme drives.
+             - set USE_KMEMLEAK=yes to scan for memory leaks in the kernel
+               after every test, if the kernel supports kmemleak.
+             - set KEEP_DMESG=yes to keep dmesg log after test
 
         - or add a case to the switch in common/config assigning
           these variables based on the hostname of your test