Ming Lei 160fcf5c6b nvme-fcloop: fix "inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage" ... [ Upstream commit 4f86a6ff6f ] fcloop_fcp_op() could be called from flush request's ->end_io(flush_end_io) in which the spinlock of fq->mq_flush_lock is grabbed with irq saved/disabled. So fcloop_fcp_op() can't call spin_unlock_irq(&tfcp_req->reqlock) simply which enables irq unconditionally. Fixes the warning by switching to spin_lock_irqsave()/spin_unlock_irqrestore() Fixes: c38dbbfab1 ("nvme-fcloop: fix inconsistent lock state warnings") Reported-by: Yi Zhang <yi.zhang@redhat.com> Signed-off-by: Ming Lei <ming.lei@redhat.com> Reviewed-by: Ewan D. Milne <emilne@redhat.com> Tested-by: Yi Zhang <yi.zhang@redhat.com> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Sasha Levin <sashal@kernel.org>		2023-05-11 23:03:22 +09:00
..
Kconfig	…
Makefile	…
admin-cmd.c	nvmet: fix I/O Command Set specific Identify Controller	2023-05-11 23:03:22 +09:00
auth.c	…
configfs.c	…
core.c	nvmet: avoid potential UAF in nvmet_req_complete()	2023-03-22 13:33:47 +01:00
discovery.c	…
fabrics-cmd-auth.c	…
fabrics-cmd.c	…
fc.c	…
fcloop.c	nvme-fcloop: fix "inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage"	2023-05-11 23:03:22 +09:00
io-cmd-bdev.c	…
io-cmd-file.c	…
loop.c	…
nvmet.h	nvmet: fix I/O Command Set specific Identify Controller	2023-05-11 23:03:22 +09:00
passthru.c	…
rdma.c	…
tcp.c	…
trace.c	…
trace.h	…
zns.c	nvmet: fix I/O Command Set specific Identify Controller	2023-05-11 23:03:22 +09:00