No, this issue has not been seen yet. Since blk_mq_run_hw_queue tests queue stopped in the very beginning. It should be possible to race with nvme_dev_disable.
I agree that the request shall be re-queued. -----Original Message----- From: Busch, Keith [mailto:keith.bu...@intel.com] Sent: Tuesday, February 2, 2016 12:00 AM To: Wenbo Wang; ax...@fb.com Cc: linux-kernel@vger.kernel.org; Wenbo Wang; linux-n...@lists.infradead.org Subject: RE: [PATCH] NVMe: do not touch sq door bell if nvmeq has been suspended Does this ever happen? The queue should be stopped before the bar is unmapped. If that's insufficient to guard against this, we've another problem this patch does not cover. That command will just timeout since it was accepted by the driver, but not actually submitted to anything. The request needs to be requeued or return BLK_MQ_RQ_QUEUE_BUSY. > -----Original Message----- > From: Wenbo Wang [mailto:mail_weber_w...@163.com] > Sent: Monday, February 01, 2016 8:42 AM > To: ax...@fb.com; Busch, Keith > Cc: linux-kernel@vger.kernel.org; Wenbo Wang; Wenbo Wang; > linux-n...@lists.infradead.org > Subject: [PATCH] NVMe: do not touch sq door bell if nvmeq has been > suspended > > If __nvme_submit_cmd races with nvme_dev_disable, nvmeq could have > been suspended and dev->bar could have been unmapped. Do not touch sq > door bell in this case. > > Signed-off-by: Wenbo Wang <wenbo.w...@memblaze.com> > Reviewed-by: Wenwei Tao <wenwei....@memblaze.com> > CC: linux-n...@lists.infradead.org > --- > drivers/nvme/host/pci.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c index > 8b1a725..2288712 100644 > --- a/drivers/nvme/host/pci.c > +++ b/drivers/nvme/host/pci.c > @@ -325,7 +325,8 @@ static void __nvme_submit_cmd(struct nvme_queue > *nvmeq, > > if (++tail == nvmeq->q_depth) > tail = 0; > - writel(tail, nvmeq->q_db); > + if (likely(nvmeq->cq_vector >= 0)) > + writel(tail, nvmeq->q_db); > nvmeq->sq_tail = tail; > } > > -- > 1.8.3.1
