| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 13 Dec 2012 00:43:10 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Jiang Liu <liuj97@...il.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
linux-pci@...r.kernel.org, Yinghai Lu <yinghai@...nel.org>,
Toshi Kani <toshi.kani@...com>,
Myron Stowe <myron.stowe@...hat.com>
Subject: [update][PATCH 1/6] ACPI: Separate adding ACPI device objects from probing ACPI drivers
On Wednesday, December 12, 2012 11:32:57 PM Rafael J. Wysocki wrote:
> On Thursday, December 13, 2012 12:38:01 AM Jiang Liu wrote:
> > On 12/10/2012 07:00 AM, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> > >
[...]
> > > static int acpi_bus_scan(acpi_handle handle, struct acpi_bus_ops *ops,
> > > struct acpi_device **child)
> > > {
> > > - acpi_status status;
> > > void *device = NULL;
> > > + acpi_status status;
> > > + int ret = 0;
> > >
> > > status = acpi_bus_check_add(handle, 0, ops, &device);
> > > - if (ACPI_SUCCESS(status))
> > > + if (ACPI_FAILURE(status)) {
> > > + ret = -ENODEV;
> > > + goto out;
> > > + }
> > > +
> > > + acpi_walk_namespace(ACPI_TYPE_ANY, handle, ACPI_UINT32_MAX,
> > > + acpi_bus_check_add, NULL, ops, &device);
> > > + if (device)
> > > acpi_walk_namespace(ACPI_TYPE_ANY, handle, ACPI_UINT32_MAX,
> > > - acpi_bus_check_add, NULL, ops, &device);
> > > + acpi_bus_probe_start, NULL, ops, NULL);
> > Hi Rafael,
> > Should we call acpi_bus_probe_start for the top device corresponding to
> > "handle" too here?
>
> Do you mean separately? I don't think so. It will be covered by the namespace
> walking, won't it?
There is one pitfall I didn't notice here, though. acpi_bus_probe_start() has
to ignore errors from acpi_bus_type_and_status(), like acpi_bus_check_add()
does, because otherwise the namespace walk may be terminated too early.
Updated patch is below and I'll need to change some other patches in the
series to take that into account.
Thanks,
Rafael
---
From: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
Subject: ACPI: Separate adding ACPI device objects from probing ACPI drivers
Currently, as soon as an ACPI device node object (struct acpi_device)
is created, the driver core attempts to probe ACPI drivers against
it. That leads to some unpleasant side effects, like the fact that
the boot code path for ACPI namespace scanning is different from the
analogous hot-plug code path (during boot ACPI drivers are not
present when ACPI device node objects are registered, so they are
guaranteed not to be probed, which is not the case during hot-plug).
That, in turn, leads to unnecessary complications in the PCI
enumeration algorithm.
Reduce the differences between the boot and hot-plug cases by
splitting the ACPI namespace scanning for devices into two passes,
such that struct acpi_device objects are registerd in the first
patch without probing ACPI drivers and the drivers are probed
against them directly in the second pass. This way ACPI drivers
can assume that all of the ACPI device node objects in the given
scope will be registered when their .add() routines run and the
hot-plug case becomes the same as the boot case from their
perspective.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
---
drivers/acpi/scan.c | 105 ++++++++++++++++++++++++++++++++++--------------
include/acpi/acpi_bus.h | 1
2 files changed, 77 insertions(+), 29 deletions(-)
Index: linux/include/acpi/acpi_bus.h
===================================================================
--- linux.orig/include/acpi/acpi_bus.h
+++ linux/include/acpi/acpi_bus.h
@@ -98,6 +98,7 @@ typedef void (*acpi_op_notify) (struct a
struct acpi_bus_ops {
u32 acpi_op_add:1;
u32 acpi_op_start:1;
+ u32 acpi_op_match:1;
};
struct acpi_device_ops {
Index: linux/drivers/acpi/scan.c
===================================================================
--- linux.orig/drivers/acpi/scan.c
+++ linux/drivers/acpi/scan.c
@@ -494,7 +494,8 @@ static int acpi_bus_match(struct device
struct acpi_device *acpi_dev = to_acpi_device(dev);
struct acpi_driver *acpi_drv = to_acpi_driver(drv);
- return !acpi_match_device_ids(acpi_dev, acpi_drv->ids);
+ return acpi_dev->bus_ops.acpi_op_match
+ && !acpi_match_device_ids(acpi_dev, acpi_drv->ids);
}
static int acpi_device_uevent(struct device *dev, struct kobj_uevent_env *env)
@@ -1418,6 +1419,17 @@ static int acpi_bus_remove(struct acpi_d
return 0;
}
+/*
+ * acpi_hot_add_bind - Bind _ADR-based devices on hot-add.
+ * @device: ACPI device node to bind.
+ */
+static void acpi_hot_add_bind(struct acpi_device *device)
+{
+ if (device->flags.bus_address
+ && device->parent && device->parent->ops.bind)
+ device->parent->ops.bind(device);
+}
+
static int acpi_add_single_object(struct acpi_device **child,
acpi_handle handle, int type,
unsigned long long sta,
@@ -1490,13 +1502,8 @@ static int acpi_add_single_object(struct
result = acpi_device_register(device);
- /*
- * Bind _ADR-Based Devices when hot add
- */
- if (device->flags.bus_address) {
- if (device->parent && device->parent->ops.bind)
- device->parent->ops.bind(device);
- }
+ if (device->bus_ops.acpi_op_match)
+ acpi_hot_add_bind(device);
end:
if (!result) {
@@ -1522,6 +1529,7 @@ static void acpi_bus_add_power_resource(
struct acpi_bus_ops ops = {
.acpi_op_add = 1,
.acpi_op_start = 1,
+ .acpi_op_match = 1,
};
struct acpi_device *device = NULL;
@@ -1574,9 +1582,9 @@ static acpi_status acpi_bus_check_add(ac
void *context, void **return_value)
{
struct acpi_bus_ops *ops = context;
+ struct acpi_device *device = NULL;
int type;
unsigned long long sta;
- struct acpi_device *device;
acpi_status status;
int result;
@@ -1600,48 +1608,86 @@ static acpi_status acpi_bus_check_add(ac
* We may already have an acpi_device from a previous enumeration. If
* so, we needn't add it again, but we may still have to start it.
*/
- device = NULL;
acpi_bus_get_device(handle, &device);
if (ops->acpi_op_add && !device) {
- acpi_add_single_object(&device, handle, type, sta, ops);
- /* Is the device a known good platform device? */
- if (device
- && !acpi_match_device_ids(device, acpi_platform_device_ids))
- acpi_create_platform_device(device);
- }
+ struct acpi_bus_ops add_ops = *ops;
- if (!device)
- return AE_CTRL_DEPTH;
-
- if (ops->acpi_op_start && !(ops->acpi_op_add)) {
- status = acpi_start_single_object(device);
- if (ACPI_FAILURE(status))
+ add_ops.acpi_op_match = 0;
+ acpi_add_single_object(&device, handle, type, sta, &add_ops);
+ if (!device)
return AE_CTRL_DEPTH;
+
+ device->bus_ops.acpi_op_match = 1;
}
if (!*return_value)
*return_value = device;
+
return AE_OK;
}
+static acpi_status acpi_bus_probe_start(acpi_handle handle, u32 lvl,
+ void *context, void **not_used)
+{
+ struct acpi_bus_ops *ops = context;
+ acpi_status status = AE_OK;
+ struct acpi_device *device;
+ unsigned long long sta_not_used;
+ int type_not_used;
+
+ /*
+ * We need to ignore errors ignored by acpi_bus_check_add() to avoid
+ * terminating namespace walks prematurely.
+ */
+ if (acpi_bus_type_and_status(handle, &type_not_used, &sta_not_used))
+ return AE_OK;
+
+ if (acpi_bus_get_device(handle, &device))
+ return AE_CTRL_DEPTH;
+
+ if (ops->acpi_op_add) {
+ if (!acpi_match_device_ids(device, acpi_platform_device_ids)) {
+ /* This is a known good platform device. */
+ acpi_create_platform_device(device);
+ } else {
+ int ret = device_attach(&device->dev);
+ acpi_hot_add_bind(device);
+ if (ret)
+ status = AE_CTRL_DEPTH;
+ }
+ } else if (ops->acpi_op_start) {
+ if (ACPI_FAILURE(acpi_start_single_object(device)))
+ status = AE_CTRL_DEPTH;
+ }
+ return status;
+}
+
static int acpi_bus_scan(acpi_handle handle, struct acpi_bus_ops *ops,
struct acpi_device **child)
{
- acpi_status status;
void *device = NULL;
+ acpi_status status;
+ int ret = 0;
status = acpi_bus_check_add(handle, 0, ops, &device);
- if (ACPI_SUCCESS(status))
+ if (ACPI_FAILURE(status)) {
+ ret = -ENODEV;
+ goto out;
+ }
+
+ acpi_walk_namespace(ACPI_TYPE_ANY, handle, ACPI_UINT32_MAX,
+ acpi_bus_check_add, NULL, ops, &device);
+ if (device)
acpi_walk_namespace(ACPI_TYPE_ANY, handle, ACPI_UINT32_MAX,
- acpi_bus_check_add, NULL, ops, &device);
+ acpi_bus_probe_start, NULL, ops, NULL);
+ else
+ ret = -ENODEV;
+ out:
if (child)
*child = device;
- if (device)
- return 0;
- else
- return -ENODEV;
+ return ret;
}
/*
@@ -1752,6 +1798,7 @@ static int acpi_bus_scan_fixed(void)
memset(&ops, 0, sizeof(ops));
ops.acpi_op_add = 1;
ops.acpi_op_start = 1;
+ ops.acpi_op_match = 1;
/*
* Enumerate all fixed-feature devices.
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists