+2
−0
Loading
SPDK NVMe driver had processed ACL as 1's based value by mistake, and SPDK NVMe-oF target sets ACL to 0. Hence If NVMe driver connects to SPDK NVMe-oF transport, spdk_nvme_ctrlr_cmd_abort() always queued abort request. Fix this bug to process ACL as 0's based value in spdk_nvme_ctrlr_cmd_abort(). Besides, initialize ACL explicitly to 0 in spdk_nvmf_ctrlr_identify_ctrlr() for clarification. Signed-off-by:Michael Haeuptle <michael.haeuptle@hpe.com> Signed-off-by:
Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Change-Id: Id4f3a469776cdab88bcc6f41e7893885a7b78d8c Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2513 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Ben Walker <benjamin.walker@intel.com> Reviewed-by:
Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com> Reviewed-by:
Michael Haeuptle <michaelhaeuptle@gmail.com>