From: Joerg Roedel <joro@8bytes.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Joerg Roedel <jroedel@suse.de>
Subject: [PATCH 2/3] ACPI: Remove platform devices from a bus on removal
Date: Wed, 22 Mar 2017 18:33:24 +0100 [thread overview]
Message-ID: <1490204005-2733-3-git-send-email-joro@8bytes.org> (raw)
In-Reply-To: <1490204005-2733-1-git-send-email-joro@8bytes.org>
From: Joerg Roedel <jroedel@suse.de>
The function acpi_bus_attach() creates platform_devices if
this is specified by the firmware. But in acpi_bus_trim()
these devices are not removed, leaving a dangling reference
to the parent device.
In the case of a PCI root-bus, this results in the
host_bridge device not being released on hot-remove.
Fix it by scanning the list of platform_devices for devices
to be removed with the bus.
Signed-off-by: Joerg Roedel <jroedel@suse.de>
---
drivers/acpi/scan.c | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/drivers/acpi/scan.c b/drivers/acpi/scan.c
index 1926918..b07518b 100644
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -13,6 +13,7 @@
#include <linux/dmi.h>
#include <linux/nls.h>
#include <linux/dma-mapping.h>
+#include <linux/platform_device.h>
#include <asm/pgtable.h>
@@ -1928,6 +1929,25 @@ int acpi_bus_scan(acpi_handle handle)
EXPORT_SYMBOL(acpi_bus_scan);
/**
+ * acpi_bus_trim_platform_device - Check and remove a platform device
+ * from a bus
+ * @dev: Platform device to check
+ * @data: pointer to the acpi_device to check dev against
+ *
+ * Checks whether the platform_device dev belongs to the acpi_device
+ * data and unregisters dev if it matches.
+ */
+static int acpi_bus_trim_platform_device(struct device *dev, void *data)
+{
+ struct acpi_device *adev = data;
+
+ if (dev->fwnode == acpi_fwnode_handle(adev))
+ platform_device_unregister(to_platform_device(dev));
+
+ return 0;
+}
+
+/**
* acpi_bus_trim - Detach scan handlers and drivers from ACPI device objects.
* @adev: Root of the ACPI namespace scope to walk.
*
@@ -1950,6 +1970,12 @@ void acpi_bus_trim(struct acpi_device *adev)
} else {
device_release_driver(&adev->dev);
}
+
+ /* Remove platform devices from the bus */
+ if (adev->pnp.type.platform_id)
+ bus_for_each_dev(&platform_bus_type, NULL, adev,
+ acpi_bus_trim_platform_device);
+
/*
* Most likely, the device is going away, so put it into D3cold before
* that.
--
1.9.1
next prev parent reply other threads:[~2017-03-22 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 17:33 [PATCH 0/3] ACPI Fixes for Hotplug Joerg Roedel
2017-03-22 17:33 ` [PATCH 1/3] ACPI, ioapic: Clear on-stack resource before using it Joerg Roedel
2017-03-22 17:33 ` Joerg Roedel [this message]
2017-04-19 6:50 ` [PATCH 2/3] ACPI: Remove platform devices from a bus on removal joeyli
2017-04-19 6:54 ` joeyli
2017-03-22 17:33 ` [PATCH 3/3] ACPI: Don't create a platform_device for IOAPIC/IOxAPIC Joerg Roedel
2017-03-22 17:42 ` Rafael J. Wysocki
2017-03-22 22:58 ` Joerg Roedel
2017-03-22 23:41 ` Rafael J. Wysocki
2017-03-22 23:44 ` Rafael J. Wysocki
2017-03-22 23:58 ` Joerg Roedel
2017-03-23 1:06 ` Rafael J. Wysocki
2017-03-23 10:50 ` Joerg Roedel
2017-03-23 11:19 ` Rafael J. Wysocki
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=1490204005-2733-3-git-send-email-joro@8bytes.org \
--to=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).