From: Gabriel Krisman Bertazi <krisman@linux.vnet.ibm.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: gregkh@linuxfoundation.org, stable@vger.kernel.org,
stewart@linux.vnet.ibm.com, mniyer@us.ibm.com,
keith.busch@intel.com
Subject: Re: [PATCH] NVMe: Don't unmap controller registers on reset
Date: Thu, 08 Sep 2016 18:10:23 -0300 [thread overview]
Message-ID: <87h99qf680.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <3616480f-2d71-e89b-cd94-91118d0e3bd1@suse.cz> (Jiri Slaby's message of "Wed, 7 Sep 2016 18:06:20 +0200")
Jiri Slaby <jslaby@suse.cz> writes:
>
>> @@ -2734,18 +2724,21 @@ static int nvme_dev_map(struct nvme_dev *dev)
>>
>> return 0;
>>
>> - unmap:
>> - iounmap(dev->bar);
>> - dev->bar = NULL;
>> disable:
>> pci_release_regions(pdev);
>> - disable_pci:
>> - pci_disable_device(pdev);
>
> Is this a correct backport?
>
> The original removes pci_release_regions, not pci_disable_device.
>
Hi Jiri,
Oh, you are correct. We need pci_disable_device here to reverse
pci_enable_device_mem on error, while should go pci_release_regions into
nvme_dev_map to reverse the pci_request_selected_regions call.
Unfortunately, my test case never touched this error path.
Greg, would you take the fix below into the -stable tree?
-- >8 --
Subject: [PATCH] nvme: Call pci_disable_device on the error path.
Commit 5706aca74fe4 ("NVMe: Don't unmap controller registers on reset"),
which backported b00a726a9fd8 to the 4.4.y kernel introduced a
regression in which it didn't call pci_disable_device in the error path
of nvme_pci_enable.
Reported-by: Jiri Slaby <jslaby@suse.cz>
Embarassed-developer: Gabriel Krisman Bertazi <krisman@linux.vnet.ibm.com>
Signed-off-by: Gabriel Krisman Bertazi <krisman@linux.vnet.ibm.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 289a5df0d44a..c851bc53831c 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -2725,7 +2725,7 @@ static int nvme_pci_enable(struct nvme_dev *dev)
return 0;
disable:
- pci_release_regions(pdev);
+ pci_disable_device(pdev);
return result;
}
--
2.7.4
next prev parent reply other threads:[~2016-09-08 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 22:06 [PATCH] NVMe: Don't unmap controller registers on reset Gabriel Krisman Bertazi
2016-09-07 16:06 ` Jiri Slaby
2016-09-08 21:10 ` Gabriel Krisman Bertazi [this message]
2016-09-09 14:37 ` Patch "nvme: Call pci_disable_device on the error path." has been added to the 4.4-stable tree gregkh
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=87h99qf680.fsf@linux.vnet.ibm.com \
--to=krisman@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=keith.busch@intel.com \
--cc=mniyer@us.ibm.com \
--cc=stable@vger.kernel.org \
--cc=stewart@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).