From: Yinghai Lu <yinghai@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Gu Zheng <guz.fnst@cn.fujitsu.com>,
Guo Chao <yan@linux.vnet.ibm.com>,
linux-pci@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH 3/6] PCI: Destroy pci dev only once
Date: Tue, 19 Nov 2013 17:51:54 -0800 [thread overview]
Message-ID: <1384912317-3721-4-git-send-email-yinghai@kernel.org> (raw)
In-Reply-To: <1384912317-3721-1-git-send-email-yinghai@kernel.org>
Mutliple removing via /sys will call pci_destroy_dev two times.
Add is_removed to record if pci_destroy_dev is called already.
During second calling, still have extra dev ref hold via
device_schedule_call, so we are safe to check dev->is_removed.
Signed-off-by: Yinghai Lu <yinghai@kernel.org>
---
drivers/pci/remove.c | 5 ++++-
include/linux/pci.h | 1 +
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/pci/remove.c b/drivers/pci/remove.c
index 0d2c36f..cffe269 100644
--- a/drivers/pci/remove.c
+++ b/drivers/pci/remove.c
@@ -20,7 +20,10 @@ static void pci_stop_dev(struct pci_dev *dev)
static void pci_destroy_dev(struct pci_dev *dev)
{
- put_device(&dev->dev);
+ if (!dev->is_removed) {
+ dev->is_removed = 1;
+ put_device(&dev->dev);
+ }
}
void pci_remove_bus(struct pci_bus *bus)
diff --git a/include/linux/pci.h b/include/linux/pci.h
index 1084a15..ccb316d 100644
--- a/include/linux/pci.h
+++ b/include/linux/pci.h
@@ -321,6 +321,7 @@ struct pci_dev {
unsigned int multifunction:1;/* Part of multi-function device */
/* keep track of device state */
unsigned int is_added:1;
+ unsigned int is_removed:1; /* pci_destroy_dev is called */
unsigned int is_busmaster:1; /* device is busmaster */
unsigned int no_msi:1; /* device may not use msi */
unsigned int block_cfg_access:1; /* config space access is blocked */
--
1.8.1.4
next prev parent reply other threads:[~2013-11-20 1:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 1:51 [PATCH 0/6] PCI: double remove fixing and allocate 64bit mmio pref Yinghai Lu
2013-11-20 1:51 ` [PATCH 1/6] PCI: move back pci_proc_attach_devices calling Yinghai Lu
2013-11-20 1:51 ` [PATCH 2/6] PCI: move resources and bus_list releasing to pci_release_dev Yinghai Lu
2013-11-20 1:51 ` Yinghai Lu [this message]
2013-11-20 1:51 ` [PATCH 4/6] PCI: pcibus address to resource converting take bus directly Yinghai Lu
2013-11-20 1:51 ` [PATCH 5/6] PCI: Add pcibios_bus_addr_to_res() Yinghai Lu
2013-11-20 1:51 ` [PATCH 6/6] PCI: Try to allocate mem64 above 4G at first Yinghai Lu
2013-11-21 10:30 ` Guo Chao
2013-11-21 20:18 ` Yinghai Lu
2013-11-21 21:05 ` Linus Torvalds
2013-11-21 21:34 ` Yinghai Lu
2013-11-21 21:42 ` Linus Torvalds
2013-11-22 6:11 ` Yinghai Lu
2013-11-22 7:08 ` Guo Chao
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=1384912317-3721-4-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=linux-pci@vger.kernel.org \
--cc=yan@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).