nvmet-fc: Fix a missed _irqsave version of spin_lock in 'nvmet_fc_fod_op_done()'
[ Upstream commit5.4-rM2-2.2.x-imx-squashed70e37988db
] The way 'spin_lock()' and 'spin_lock_irqsave()' are used is not consistent in this function. Use 'spin_lock_irqsave()' also here, as there is no guarantee that interruptions are disabled at that point, according to surrounding code. Fixes:a97ec51b37
("nvmet_fc: Rework target side abort handling") Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Sasha Levin <sashal@kernel.org>
parent
9ff9f74ed4
commit
f4b830c61b
|
@ -1994,9 +1994,9 @@ nvmet_fc_fod_op_done(struct nvmet_fc_fcp_iod *fod)
|
|||
return;
|
||||
if (fcpreq->fcp_error ||
|
||||
fcpreq->transferred_length != fcpreq->transfer_length) {
|
||||
spin_lock(&fod->flock);
|
||||
spin_lock_irqsave(&fod->flock, flags);
|
||||
fod->abort = true;
|
||||
spin_unlock(&fod->flock);
|
||||
spin_unlock_irqrestore(&fod->flock, flags);
|
||||
|
||||
nvmet_req_complete(&fod->req, NVME_SC_INTERNAL);
|
||||
return;
|
||||
|
|
Loading…
Reference in New Issue