diff options
| author | Ming Lei <ming.lei@redhat.com> | 2023-04-12 16:49:04 +0800 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2023-04-13 09:02:55 +0200 |
| commit | 4f86a6ff6fbd891232dda3ca97fd1b9630b59809 (patch) | |
| tree | b003cedaeea756f6b2368cea9087d7b388cc0936 /block | |
| parent | edde9e70bb48301c853299f1bd7c0aa0745a38ea (diff) | |
| download | linux-stable-4f86a6ff6fbd891232dda3ca97fd1b9630b59809.tar.gz linux-stable-4f86a6ff6fbd891232dda3ca97fd1b9630b59809.tar.bz2 linux-stable-4f86a6ff6fbd891232dda3ca97fd1b9630b59809.zip | |
nvme-fcloop: fix "inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage"
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: c38dbbfab1bc ("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>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions