diff options
| author | Ming Lei <ming.lei@redhat.com> | 2023-04-12 16:49:04 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2023-05-11 23:03:22 +0900 |
| commit | 160fcf5c6b17df1b3178de1c8df253c3f6d5fe71 (patch) | |
| tree | 27d74bb2c6e28a51f32235b439b981131053df10 /tools | |
| parent | 0f1c4ae80d142bcf0f231a929e4aedb0731e1346 (diff) | |
| download | linux-stable-160fcf5c6b17df1b3178de1c8df253c3f6d5fe71.tar.gz linux-stable-160fcf5c6b17df1b3178de1c8df253c3f6d5fe71.tar.bz2 linux-stable-160fcf5c6b17df1b3178de1c8df253c3f6d5fe71.zip | |
nvme-fcloop: fix "inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage"
[ Upstream commit 4f86a6ff6fbd891232dda3ca97fd1b9630b59809 ]
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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions