summaryrefslogtreecommitdiffstats
path: root/arch/s390
diff options
context:
space:
mode:
authorYu Kuai <yukuai3@huawei.com>2021-09-16 17:33:45 +0800
committerJens Axboe <axboe@kernel.dk>2021-10-18 14:50:37 -0600
commit07175cb1baf4c51051b1fbd391097e349f9a02a9 (patch)
tree4477c81e951af1fd4c0ab72213376b314a529db3 /arch/s390
parent4e6eef5dc25b528e08ac5b5f64f6ca9d9987241d (diff)
downloadlinux-07175cb1baf4c51051b1fbd391097e349f9a02a9.tar.bz2
nbd: make sure request completion won't concurrent
commit cddce0116058 ("nbd: Aovid double completion of a request") try to fix that nbd_clear_que() and recv_work() can complete a request concurrently. However, the problem still exists: t1 t2 t3 nbd_disconnect_and_put flush_workqueue recv_work blk_mq_complete_request blk_mq_complete_request_remote -> this is true WRITE_ONCE(rq->state, MQ_RQ_COMPLETE) blk_mq_raise_softirq blk_done_softirq blk_complete_reqs nbd_complete_rq blk_mq_end_request blk_mq_free_request WRITE_ONCE(rq->state, MQ_RQ_IDLE) nbd_clear_que blk_mq_tagset_busy_iter nbd_clear_req __blk_mq_free_request blk_mq_put_tag blk_mq_complete_request -> complete again There are three places where request can be completed in nbd: recv_work(), nbd_clear_que() and nbd_xmit_timeout(). Since they all hold cmd->lock before completing the request, it's easy to avoid the problem by setting and checking a cmd flag. Signed-off-by: Yu Kuai <yukuai3@huawei.com> Reviewed-by: Ming Lei <ming.lei@redhat.com> Reviewed-by: Josef Bacik <josef@toxicpanda.com> Link: https://lore.kernel.org/r/20210916093350.1410403-3-yukuai3@huawei.com Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'arch/s390')
0 files changed, 0 insertions, 0 deletions