Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe: Unbind driver on failure
Date: Tue, 26 Apr 2016 20:15:18 +0000	[thread overview]
Message-ID: <20160426201517.GE21270@localhost.localdomain> (raw)
In-Reply-To: <1459201359-25044-1-git-send-email-keith.busch@intel.com>

ping

On Mon, Mar 28, 2016@03:42:39PM -0600, Keith Busch wrote:
> Instead of removing the PCI device from the kernel's topology on
> controller failure, this patch simply requests unbinding the device
> from the driver. This avoids concurrently running pci removal with the
> hot plug event, which has been reported to be problematic when multiple
> surprise events occur near simultaneously.
> 
> The other benefit is that we will have PCI config and memory space
> available to poke around for debugging a failed controller, assuming
> the device was not physically removed.
> 
> The down side occurs if the platform and/or kernel do not support any
> type of surprise hot removal. The device will remain visible through
> sysfs (and therefore lspci), and some manual work is necessary to get
> the logical topology corrected. But if your platform and/or kernel don't
> support surprise removal, you probably shouldn't be doing that anyway.
> 
> Signed-off-by: Keith Busch <keith.busch at intel.com>
> ---
>  drivers/nvme/host/pci.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 660ec84..5acd6e4 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -1916,7 +1916,7 @@ static void nvme_remove_dead_ctrl_work(struct work_struct *work)
>  
>  	nvme_kill_queues(&dev->ctrl);
>  	if (pci_get_drvdata(pdev))
> -		pci_stop_and_remove_bus_device_locked(pdev);
> +		device_release_driver(&pdev->dev);
>  	nvme_put_ctrl(&dev->ctrl);
>  }
>  
> -- 
> 2.7.2

      parent reply	other threads:[~2016-04-26 20:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-28 21:42 [PATCH] NVMe: Unbind driver on failure Keith Busch
2016-03-29  7:03 ` Christoph Hellwig
2016-04-03 16:33 ` sagig
2016-04-26 20:15 ` Keith Busch [this message]

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=20160426201517.GE21270@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox