diff options
author | 2023-04-06 23:39:11 +0800 | |
---|---|---|
committer | 2023-04-13 08:59:04 +0200 | |
commit | d4f1d5f7a4d8d998739c3d699476cd0247d580c6 (patch) | |
tree | 518b4edaae3d735b7e407a4f2343b6718eb6bbbf /tools/perf/scripts/python/export-to-postgresql.py | |
parent | nvme: fix async event trace event (diff) | |
download | wireguard-linux-d4f1d5f7a4d8d998739c3d699476cd0247d580c6.tar.xz wireguard-linux-d4f1d5f7a4d8d998739c3d699476cd0247d580c6.zip |
nvme: fix double blk_mq_complete_request for timeout request with low probability
When nvme_cancel_tagset traverses all tagsets and executes
nvme_cancel_request, this request may be executing blk_mq_free_request
that is called by nvme_rdma_complete_timed_out/nvme_tcp_complete_timed_out.
When blk_mq_free_request executes to WRITE_ONCE(rq->state, MQ_RQ_IDLE) and
__blk_mq_free_request(rq), it will cause double blk_mq_complete_request for
this request, and it will cause a null pointer error in the second
execution of this function because rq->mq_hctx has set to NULL in first
execution.
Signed-off-by: Lei Yin <yinlei2@lenovo.com>
Reviewed-by: Keith Busch <kbusch@kernel.org>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions