Hi Ming On 05/02/2018 12:54 PM, Ming Lei wrote: >> We need to return BLK_EH_RESET_TIMER in nvme_timeout then: >> 1. defer the completion. we can't unmap the io request before close the >> controller totally, so not BLK_EH_HANDLED. >> 2. nvme_cancel_request could complete it. blk_mq_complete_request is invoked >> by nvme_cancel_request, so not BLK_EH_NOT_HANDLED. > We don't need to change return value of .timeout() any more after > calling nvme_quiesce_timeout(): > > Thanks the single EH kthread, once nvme_quiesce_timeout() returns, all > timed-out requests have been handled already. Some of them may be completed, > and others may be handled as RESET_TIMER, but none of them are handled as > NOT_HANDLED because nvme_timeout() won't return that value. > > So the following blk_mq_tagset_busy_iter(nvme_cancel_request) can handle > all in-flight requests because timeout is drained and quiesced.
The key point here is we cannot unmap the io requests before we close the controller directly. The nvme controller may still hold the command after we complete and unmap the io request in nvme_timeout. This will cause memory corruption. So we cannot just schedule the eh recovery kthread then return BLK_EH_HANDLED. We need to deffer the completion of timeout requests until the controller has been closed totally in nvme_dev_disable. Thanks Jianchao
