check: try reloading modules
PATCH v2 24/24 check: try reloading modules
From: Darrick J. Wong <[email protected]>
Optionally reload the module between each test to try to pinpoint slab cache errors and whatnot.
Signed-off-by Darrick J. Wong <[email protected]>
---
v2: use "fs-$FSTYP" for the module name
--- README | 3 +++ check | 9 +++++++++ 2 files changed, 12 insertions(+)
README +3 -0
@@ -106,6 +106,9 @@ Preparing system for tests: - 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 + - Set TEST_FS_MODULE_RELOAD=1 to unload the module and reload + it between test invocations. This assumes that the name of + the module is the same as FSTYP. - or add a case to the switch in common/config assigning these variables based on the hostname of your test
check +9 -0
@@ -834,6 +834,15 @@ function run_section() _check_dmesg || err=true fi + # Reload the module after each test to check for leaks or + # other problems. + if [ -n "${TEST_FS_MODULE_RELOAD}" ]; then + _test_unmount 2> /dev/null + _scratch_unmount 2> /dev/null + modprobe -r fs-$FSTYP + modprobe fs-$FSTYP + fi + # Scan for memory leaks after every test so that associating # a leak to a particular test will be as accurate as possible. _check_kmemleak || err=true