All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 5/5] nvme/pci: Complete all stuck requests
Date: Wed, 15 Feb 2017 10:46:49 -0500	[thread overview]
Message-ID: <20170215154649.GA30251@localhost.localdomain> (raw)
In-Reply-To: <c42e8e1e-f96f-9b2d-f3e6-72599430a327@grimberg.me>

On Wed, Feb 15, 2017@11:50:15AM +0200, Sagi Grimberg wrote:
> How is this is something specific to nvme? What prevents this
> for other multi-queue devices that shutdown during live IO?
> 
> Can you please describe the race in specific? Is it stuck on
> nvme_ns_remove (blk_cleanup_queue)? If so, then I think we
> might want to fix blk_cleanup_queue to start/drain/wait
> instead?
> 
> I think it's acceptable to have drivers make their own use
> of freeze_start and freeze_wait, but if this is not
> nvme specific perhaps we want to move it to block instead?

There are many sequences that can get a request queue stuck forever, but
the one that was initially raised is on a system suspend. It could look
something like this:

  CPU A                       CPU B
  -----                       -----
  nvme_suspend
   nvme_dev_disable           generic_make_request
    nvme_stop_queues           blk_queue_enter
     blk_queue_quiesce_queue    blk_mq_alloc_request
                                 blk_mq_map_request
                                  blk_mq_enter_live
                                 blk_mq_run_hw_queue <-- the hctx is stopped,
                                                         request is stuck until
                                                         restarted.

Shortly later, suspend takes a CPU offline:

 blk_mq_queue_reinit_dead
  blk_mq_queue_reinit_work
   blk_mq_free_queue_wait

Now we're stuck forever waiting for that queue to freeze because a request
entered a stopped hctx that we're not going to bring back online. The
driver was told to suspend, and suspend must complete before resume
can start.

The problem is not specific to pci nvme, but control needs to pass back to
the device specific driver: after halting new queue entering by starting
the queue freeze, the driver needs a chance to complete everything that
was submitted. Only after the driver finishes its specific clean up tasks,
it can flush all the entered requests to a failed completion.

  reply	other threads:[~2017-02-15 15:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 23:15 [PATCH 0/5] NVMe pci fixes, for-4.11 Keith Busch
2017-02-10 23:15 ` [PATCH 1/5] nvme/pci: Disable on removal when disconnected Keith Busch
2017-02-13 10:18   ` Johannes Thumshirn
2017-02-13 13:51   ` Christoph Hellwig
2017-02-10 23:15 ` [PATCH 2/5] nvme/pci: Cancel work after watchdog disabled Keith Busch
2017-02-13 10:25   ` Johannes Thumshirn
2017-02-13 13:51   ` Christoph Hellwig
2017-02-10 23:15 ` [PATCH 3/5] nvme/core: Fix race kicking freed request_queue Keith Busch
2017-02-13 10:33   ` Johannes Thumshirn
2017-02-13 13:53   ` Christoph Hellwig
2017-02-10 23:15 ` [PATCH 4/5] nvme/pci: No special case for queue busy on IO Keith Busch
2017-02-13 13:53   ` Christoph Hellwig
2017-02-10 23:15 ` [PATCH 5/5] nvme/pci: Complete all stuck requests Keith Busch
2017-02-15  9:50   ` Sagi Grimberg
2017-02-15 15:46     ` Keith Busch [this message]
2017-02-15 16:04       ` Marc MERLIN
2017-02-15 17:36         ` J Freyensee
2017-02-16  9:12         ` Sagi Grimberg
2017-02-16 22:51           ` Keith Busch
2017-02-17  8:25             ` Christoph Hellwig
2017-02-15 18:14   ` Marc MERLIN
2017-12-14  3:36     ` Marc MERLIN
2018-02-28  2:22       ` Marc MERLIN
2017-02-17 15:27   ` Christoph Hellwig
2017-02-17 16:33     ` Keith Busch
2017-02-20 10:05       ` Christoph Hellwig
2017-02-21 15:57         ` Keith Busch
2017-02-22  7:17           ` Christoph Hellwig
2017-02-22 14:45             ` Keith Busch
2017-02-23 15:06               ` Christoph Hellwig
2017-02-23 15:21                 ` Keith Busch
2017-02-23 15:16                   ` Christoph Hellwig
2017-02-21 21:55       ` Sagi Grimberg
2017-02-21 23:26         ` Keith Busch
2017-02-15  9:40 ` [PATCH 0/5] NVMe pci fixes, for-4.11 Sagi Grimberg
     [not found] <20170313153319.fmy6ww72fjtx74xq@merlins.org>
     [not found] ` <20170313143649.GC6994@localhost.localdomain>

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170215154649.GA30251@localhost.localdomain \
    --to=keith.busch@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.