Commit 79aac783 authored Jul 29, 2020 by Seth Howell Committed by Tomasz Zawadzki Jul 31, 2020

test/nvmf: don't use Soft-RoCE in Shutdown tests.



Soft-RoCE sometimes returns non-spec compliant values
in the WC entries after the qpair has been disconnected.
This can result in segmentation faults. In order to avoid
this, don't test shutdown on Soft-RoCE.

Signed-off-by: Seth Howell <seth.howell@intel.com>
Change-Id: I604ffaf38aa8da5efa349df0b1b51e7e391d17f8
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3582


Community-CI: Mellanox Build Bot
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Jim Harris <james.r.harris@intel.com>

parent 144068a9

test/nvmf/target/shutdown.sh

+8 −0

Original line number	Diff line number	Diff line
		@@ -146,6 +146,14 @@ function nvmf_shutdown_tc3() {
		stoptarget
		}

		# The shutdown tests create a lot of edge cases that Soft-RoCE doesn't respond well to.
		# Specifically Soft-RoCE will return invalid values in the WC field after a qp has been
		# destroyed which lead to NULL pointer references not seen in real hardware.
		if [ $TEST_TRANSPORT == "rdma" ] && check_ip_is_soft_roce $NVMF_FIRST_TARGET_IP; then
		echo "Using software RDMA, skipping the shutdown tests."
		exit 0
		fi

		nvmftestinit

		run_test "nvmf_shutdown_tc1" nvmf_shutdown_tc1