[PATCH] generic/270: kill fsstress by exact name

Andrey Albershteyn <[email protected]> Thu, 9 Jul 2026 13:18:47 +0200
Newsgroups org.kernel.vger.fstests
Message-ID <[email protected]>
Running ./check with fsstress in the arguments (for example -x
fsstress_scrub) causes pkill to kill parent bash process executing the
tests. The test suite execution just stops with:

xfstests-start[4099970]: Terminated                 _run_seq 2>&1 | tee $tmp.out
xfstests-start[4099970]: Ran: generic/269 generic/270
xfstests-start[4102535]: Interrupted!
xfstests-start[4102538]: Interrupted!

Fix by using exact name, we can not use _pkill_fsstress here as this
test copies fsstress binary under custom name.

Signed-off-by: Andrey Albershteyn <[email protected]>
---
 tests/generic/270 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/generic/270 b/tests/generic/270
index 9ac829a7379f..73464f02d3d9 100755
--- a/tests/generic/270
+++ b/tests/generic/270
@@ -50,7 +50,7 @@ _workout()
 		sleep $enospc_time
 	done
 
-	_pkill -PIPE -f fsstress
+	_pkill -PIPE -f "$tmp.fsstress.bin"
 	wait $_FSSTRESS_PID
 	return 0
 }
-- 
2.54.0