On 5/29/2020 4:37 AM, Daniel Wagner wrote:
Asynchronous event notifications do not have an request associated. When fcp_io() fails we unconditionally call nvme_cleanup_cmd() which leads to a crash. Fixes: 16686f3a6c3c ("nvme: move common call to nvme_cleanup_cmd to core layer") Cc: Max Gurtovoy <m...@mellanox.com> Signed-off-by: Daniel Wagner <dwag...@suse.de> --- drivers/nvme/host/fc.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c index 7dfc4a2ecf1e..287a3e8ea317 100644 --- a/drivers/nvme/host/fc.c +++ b/drivers/nvme/host/fc.c @@ -2300,10 +2300,11 @@ nvme_fc_start_fcp_op(struct nvme_fc_ctrl *ctrl, struct nvme_fc_queue *queue, opstate = atomic_xchg(&op->state, FCPOP_STATE_COMPLETE); __nvme_fc_fcpop_chk_teardowns(ctrl, op, opstate);- if (!(op->flags & FCOP_FLAGS_AEN))+ if (!(op->flags & FCOP_FLAGS_AEN)) { nvme_fc_unmap_data(ctrl, op->rq, op); + nvme_cleanup_cmd(op->rq); + }- nvme_cleanup_cmd(op->rq);nvme_fc_ctrl_put(ctrl);if (ctrl->rport->remoteport.port_state == FC_OBJSTATE_ONLINE &&
Reviewed-by: James Smart <james.sm...@broadcom.com> -- james
