ublk_drv may be built-in, so don't show modprobe failure, and we do check `/dev/ublk-control` for skipping test if ublk_drv isn't enabled. Reported-by: Jens Axboe <axboe@xxxxxxxxx> Signed-off-by: Ming Lei <ming.lei@xxxxxxxxxx> --- tools/testing/selftests/ublk/test_common.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/ublk/test_common.sh b/tools/testing/selftests/ublk/test_common.sh index 350380facd9f..c86363c5cc7e 100755 --- a/tools/testing/selftests/ublk/test_common.sh +++ b/tools/testing/selftests/ublk/test_common.sh @@ -64,7 +64,7 @@ _check_root() { _remove_ublk_devices() { ${UBLK_PROG} del -a - modprobe -r ublk_drv + modprobe -r ublk_drv > /dev/null 2>&1 } _get_ublk_dev_state() { @@ -79,7 +79,7 @@ _prep_test() { _check_root local type=$1 shift 1 - modprobe ublk_drv + modprobe ublk_drv > /dev/null 2>&1 [ "$UBLK_TEST_QUIET" -eq 0 ] && echo "ublk $type: $*" } -- 2.47.0