diff options
author | Luís Henriques <lhenriques@suse.de> | 2023-07-13 09:26:31 +0100 |
---|---|---|
committer | Zorro Lang <zlang@kernel.org> | 2023-07-23 12:56:22 +0800 |
commit | 05574f3cfc49df09af8d98b68db5e44a4cf9c0ee (patch) | |
tree | 15ca6312c9d33d2b72625d581b8df6f4485912f0 | |
parent | f2c9af189a76ecd0920466fb4afd8e542a5dc5e9 (diff) | |
download | xfstests-dev-05574f3cfc49df09af8d98b68db5e44a4cf9c0ee.tar.gz |
common/rc: cleanup old .kmemleak files
I've spent a non-negligible amount of time looking into a kmemleak that
didn't exist in the code I was testing because there was an old .kmemleak
file in the results directory. I don't think this is an intended behaviour,
so I'm proposing to remove these files everytime we capture the result of a
new scan.
Signed-off-by: Luís Henriques <lhenriques@suse.de>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Zorro Lang <zlang@kernel.org>
-rw-r--r-- | common/rc | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -4433,6 +4433,10 @@ _capture_kmemleak() local kern_knob="$DEBUGFS_MNT/kmemleak" local leak_file="$1" + # Some callers pass in /dev/null when they want to clear the + # kernel's leak report file and do not care what was in that. + [ -f "$leak_file" ] && rm -f "$leak_file" + # Tell the kernel to scan for memory leaks. Apparently the write # returns before the scan is complete, so do it twice in the hopes # that twice is enough to capture all the leaks. |