+0
−1
+2
−1
+0
−1
Loading
All existing callers of nvme_complete_request also immediately call nvme_free_request as well. So just free the request inside of nvme_complete_request. nvme_tcp_req_complete() was the exception here. Commit 21d15cb0 tried to support immediately reusing a completed req, by calling nvme_complete_request *before* nvme_free_request. This is non-intuitive, and actually breaks an upcoming patch needed to fix a different issue. This patch removes this non-intuitive ordering. Fixes commit 21d15cb0 ("nvme: cache values in nvme_tcp_req_complete") Signed-off-by:Jim Harris <jim.harris@samsung.com> Change-Id: Iee5ce0ebd03ce0eef29399a45359ffd6f56c44e7 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20648 Reviewed-by:
Aleksey Marchuk <alexeymar@nvidia.com> Reviewed-by:
Vasuki Manikarnike <vasuki.manikarnike@hpe.com> Community-CI: Mellanox Build Bot Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Ben Walker <ben@nvidia.com>