2006-07-10 05:22:28 +08:00
|
|
|
/*
|
|
|
|
* dock.c - ACPI dock station driver
|
|
|
|
*
|
|
|
|
* Copyright (C) 2006 Kristen Carlson Accardi <kristen.c.accardi@intel.com>
|
|
|
|
*
|
|
|
|
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation; either version 2 of the License, or (at
|
|
|
|
* your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful, but
|
|
|
|
* WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License along
|
|
|
|
* with this program; if not, write to the Free Software Foundation, Inc.,
|
|
|
|
* 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
|
|
|
|
*
|
|
|
|
* ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/module.h>
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 16:04:11 +08:00
|
|
|
#include <linux/slab.h>
|
2006-07-10 05:22:28 +08:00
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/types.h>
|
|
|
|
#include <linux/notifier.h>
|
2006-12-05 06:49:43 +08:00
|
|
|
#include <linux/platform_device.h>
|
2006-10-19 01:55:46 +08:00
|
|
|
#include <linux/jiffies.h>
|
2007-03-27 13:38:49 +08:00
|
|
|
#include <linux/stddef.h>
|
2012-11-21 07:42:30 +08:00
|
|
|
#include <linux/acpi.h>
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2013-12-17 17:30:04 +08:00
|
|
|
#include "internal.h"
|
|
|
|
|
2009-07-29 04:45:54 +08:00
|
|
|
#define PREFIX "ACPI: "
|
|
|
|
|
2007-02-13 12:50:02 +08:00
|
|
|
#define ACPI_DOCK_DRIVER_DESCRIPTION "ACPI Dock Station Driver"
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2007-02-13 11:42:12 +08:00
|
|
|
ACPI_MODULE_NAME("dock");
|
2006-07-10 05:22:28 +08:00
|
|
|
MODULE_AUTHOR("Kristen Carlson Accardi");
|
2007-02-13 12:50:02 +08:00
|
|
|
MODULE_DESCRIPTION(ACPI_DOCK_DRIVER_DESCRIPTION);
|
2006-07-10 05:22:28 +08:00
|
|
|
MODULE_LICENSE("GPL");
|
|
|
|
|
2012-01-13 07:02:20 +08:00
|
|
|
static bool immediate_undock = 1;
|
2007-05-10 06:08:15 +08:00
|
|
|
module_param(immediate_undock, bool, 0644);
|
|
|
|
MODULE_PARM_DESC(immediate_undock, "1 (default) will cause the driver to "
|
|
|
|
"undock immediately when the undock button is pressed, 0 will cause"
|
|
|
|
" the driver to wait for userspace to write the undock sysfs file "
|
|
|
|
" before undocking");
|
|
|
|
|
2007-12-07 20:20:42 +08:00
|
|
|
static const struct acpi_device_id dock_device_ids[] = {
|
|
|
|
{"LNXDOCK", 0},
|
|
|
|
{"", 0},
|
|
|
|
};
|
|
|
|
MODULE_DEVICE_TABLE(acpi, dock_device_ids);
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
struct dock_station {
|
|
|
|
acpi_handle handle;
|
|
|
|
unsigned long last_dock_time;
|
|
|
|
u32 flags;
|
|
|
|
struct list_head dependent_devices;
|
2008-08-28 10:03:58 +08:00
|
|
|
|
2009-10-02 01:59:23 +08:00
|
|
|
struct list_head sibling;
|
2008-08-28 10:03:58 +08:00
|
|
|
struct platform_device *dock_device;
|
2006-07-10 05:22:28 +08:00
|
|
|
};
|
2008-08-28 10:03:58 +08:00
|
|
|
static LIST_HEAD(dock_stations);
|
|
|
|
static int dock_station_count;
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
static DEFINE_MUTEX(hotplug_lock);
|
2006-07-10 05:22:28 +08:00
|
|
|
|
|
|
|
struct dock_dependent_device {
|
|
|
|
struct list_head list;
|
|
|
|
acpi_handle handle;
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
const struct acpi_dock_ops *hp_ops;
|
|
|
|
void *hp_context;
|
|
|
|
unsigned int hp_refcount;
|
|
|
|
void (*hp_release)(void *);
|
2006-07-10 05:22:28 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
#define DOCK_DOCKING 0x00000001
|
2007-05-10 06:08:15 +08:00
|
|
|
#define DOCK_UNDOCKING 0x00000002
|
2008-08-28 10:03:58 +08:00
|
|
|
#define DOCK_IS_DOCK 0x00000010
|
|
|
|
#define DOCK_IS_ATA 0x00000020
|
|
|
|
#define DOCK_IS_BAT 0x00000040
|
2006-08-02 05:59:19 +08:00
|
|
|
#define DOCK_EVENT 3
|
|
|
|
#define UNDOCK_EVENT 2
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2013-07-05 09:03:25 +08:00
|
|
|
enum dock_callback_type {
|
|
|
|
DOCK_CALL_HANDLER,
|
|
|
|
DOCK_CALL_FIXUP,
|
|
|
|
DOCK_CALL_UEVENT,
|
|
|
|
};
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
/*****************************************************************************
|
|
|
|
* Dock Dependent device functions *
|
|
|
|
*****************************************************************************/
|
|
|
|
/**
|
2009-10-20 05:14:29 +08:00
|
|
|
* add_dock_dependent_device - associate a device with the dock station
|
|
|
|
* @ds: The dock station
|
|
|
|
* @handle: handle of the dependent device
|
2006-07-10 05:22:28 +08:00
|
|
|
*
|
2009-10-20 05:14:29 +08:00
|
|
|
* Add the dependent device to the dock's dependent device list.
|
2006-07-10 05:22:28 +08:00
|
|
|
*/
|
2013-06-29 00:24:36 +08:00
|
|
|
static int __init
|
2009-10-20 05:14:29 +08:00
|
|
|
add_dock_dependent_device(struct dock_station *ds, acpi_handle handle)
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
|
|
|
struct dock_dependent_device *dd;
|
|
|
|
|
|
|
|
dd = kzalloc(sizeof(*dd), GFP_KERNEL);
|
2009-10-20 05:14:29 +08:00
|
|
|
if (!dd)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
|
|
|
dd->handle = handle;
|
|
|
|
INIT_LIST_HEAD(&dd->list);
|
2006-07-10 05:22:28 +08:00
|
|
|
list_add_tail(&dd->list, &ds->dependent_devices);
|
2009-10-20 05:14:29 +08:00
|
|
|
|
|
|
|
return 0;
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
2013-07-01 05:50:24 +08:00
|
|
|
static void remove_dock_dependent_devices(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
struct dock_dependent_device *dd, *aux;
|
|
|
|
|
|
|
|
list_for_each_entry_safe(dd, aux, &ds->dependent_devices, list) {
|
|
|
|
list_del(&dd->list);
|
|
|
|
kfree(dd);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
/**
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
* dock_init_hotplug - Initialize a hotplug device on a docking station.
|
|
|
|
* @dd: Dock-dependent device.
|
|
|
|
* @ops: Dock operations to attach to the dependent device.
|
|
|
|
* @context: Data to pass to the @ops callbacks and @release.
|
|
|
|
* @init: Optional initialization routine to run after setting up context.
|
|
|
|
* @release: Optional release routine to run on removal.
|
2006-07-10 05:22:28 +08:00
|
|
|
*/
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
static int dock_init_hotplug(struct dock_dependent_device *dd,
|
|
|
|
const struct acpi_dock_ops *ops, void *context,
|
|
|
|
void (*init)(void *), void (*release)(void *))
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
mutex_lock(&hotplug_lock);
|
2013-07-01 05:47:14 +08:00
|
|
|
if (WARN_ON(dd->hp_context)) {
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
ret = -EEXIST;
|
|
|
|
} else {
|
|
|
|
dd->hp_refcount = 1;
|
|
|
|
dd->hp_ops = ops;
|
|
|
|
dd->hp_context = context;
|
|
|
|
dd->hp_release = release;
|
2013-07-01 05:47:14 +08:00
|
|
|
if (init)
|
|
|
|
init(context);
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
}
|
|
|
|
mutex_unlock(&hotplug_lock);
|
|
|
|
return ret;
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
* dock_release_hotplug - Decrement hotplug reference counter of dock device.
|
|
|
|
* @dd: Dock-dependent device.
|
2006-07-10 05:22:28 +08:00
|
|
|
*
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
* Decrement the reference counter of @dd and if 0, detach its hotplug
|
|
|
|
* operations from it, reset its context pointer and run the optional release
|
|
|
|
* routine if present.
|
2006-07-10 05:22:28 +08:00
|
|
|
*/
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
static void dock_release_hotplug(struct dock_dependent_device *dd)
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
mutex_lock(&hotplug_lock);
|
|
|
|
if (dd->hp_context && !--dd->hp_refcount) {
|
2013-07-01 05:47:14 +08:00
|
|
|
void (*release)(void *) = dd->hp_release;
|
|
|
|
void *context = dd->hp_context;
|
|
|
|
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
dd->hp_ops = NULL;
|
|
|
|
dd->hp_context = NULL;
|
|
|
|
dd->hp_release = NULL;
|
2013-07-01 05:47:14 +08:00
|
|
|
if (release)
|
|
|
|
release(context);
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
}
|
|
|
|
mutex_unlock(&hotplug_lock);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void dock_hotplug_event(struct dock_dependent_device *dd, u32 event,
|
2013-07-05 09:03:25 +08:00
|
|
|
enum dock_callback_type cb_type)
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
{
|
|
|
|
acpi_notify_handler cb = NULL;
|
|
|
|
bool run = false;
|
|
|
|
|
|
|
|
mutex_lock(&hotplug_lock);
|
|
|
|
|
|
|
|
if (dd->hp_context) {
|
|
|
|
run = true;
|
|
|
|
dd->hp_refcount++;
|
2013-07-05 09:03:25 +08:00
|
|
|
if (dd->hp_ops) {
|
|
|
|
switch (cb_type) {
|
|
|
|
case DOCK_CALL_FIXUP:
|
|
|
|
cb = dd->hp_ops->fixup;
|
|
|
|
break;
|
|
|
|
case DOCK_CALL_UEVENT:
|
|
|
|
cb = dd->hp_ops->uevent;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
cb = dd->hp_ops->handler;
|
|
|
|
}
|
|
|
|
}
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
mutex_unlock(&hotplug_lock);
|
|
|
|
|
|
|
|
if (!run)
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (cb)
|
|
|
|
cb(dd->handle, event, dd->hp_context);
|
|
|
|
|
|
|
|
dock_release_hotplug(dd);
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* find_dock_dependent_device - get a device dependent on this dock
|
|
|
|
* @ds: the dock station
|
|
|
|
* @handle: the acpi_handle of the device we want
|
|
|
|
*
|
|
|
|
* iterate over the dependent device list for this dock. If the
|
|
|
|
* dependent device matches the handle, return.
|
|
|
|
*/
|
|
|
|
static struct dock_dependent_device *
|
|
|
|
find_dock_dependent_device(struct dock_station *ds, acpi_handle handle)
|
|
|
|
{
|
|
|
|
struct dock_dependent_device *dd;
|
|
|
|
|
2013-06-29 00:24:35 +08:00
|
|
|
list_for_each_entry(dd, &ds->dependent_devices, list)
|
|
|
|
if (handle == dd->handle)
|
2006-07-10 05:22:28 +08:00
|
|
|
return dd;
|
2013-06-29 00:24:35 +08:00
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*****************************************************************************
|
|
|
|
* Dock functions *
|
|
|
|
*****************************************************************************/
|
2013-06-29 00:24:36 +08:00
|
|
|
static int __init is_battery(acpi_handle handle)
|
2008-08-28 10:03:58 +08:00
|
|
|
{
|
|
|
|
struct acpi_device_info *info;
|
|
|
|
int ret = 1;
|
|
|
|
|
2009-06-29 13:39:29 +08:00
|
|
|
if (!ACPI_SUCCESS(acpi_get_object_info(handle, &info)))
|
2008-08-28 10:03:58 +08:00
|
|
|
return 0;
|
|
|
|
if (!(info->valid & ACPI_VALID_HID))
|
|
|
|
ret = 0;
|
|
|
|
else
|
2009-06-29 13:39:29 +08:00
|
|
|
ret = !strcmp("PNP0C0A", info->hardware_id.string);
|
2008-08-28 10:03:58 +08:00
|
|
|
|
2009-06-29 13:39:29 +08:00
|
|
|
kfree(info);
|
2008-08-28 10:03:58 +08:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2013-06-29 00:24:42 +08:00
|
|
|
/* Check whether ACPI object is an ejectable battery or disk bay */
|
|
|
|
static bool __init is_ejectable_bay(acpi_handle handle)
|
2008-08-28 10:03:58 +08:00
|
|
|
{
|
2013-06-29 00:24:42 +08:00
|
|
|
if (acpi_has_method(handle, "_EJ0") && is_battery(handle))
|
|
|
|
return true;
|
2009-10-20 05:14:50 +08:00
|
|
|
|
2013-06-29 00:24:42 +08:00
|
|
|
return acpi_bay_match(handle);
|
2008-08-28 10:03:58 +08:00
|
|
|
}
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
/**
|
|
|
|
* is_dock_device - see if a device is on a dock station
|
|
|
|
* @handle: acpi handle of the device
|
|
|
|
*
|
|
|
|
* If this device is either the dock station itself,
|
|
|
|
* or is a device dependent on the dock station, then it
|
|
|
|
* is a dock device
|
|
|
|
*/
|
|
|
|
int is_dock_device(acpi_handle handle)
|
|
|
|
{
|
2008-08-28 10:03:58 +08:00
|
|
|
struct dock_station *dock_station;
|
|
|
|
|
|
|
|
if (!dock_station_count)
|
2006-07-10 05:22:28 +08:00
|
|
|
return 0;
|
|
|
|
|
2013-06-29 00:24:42 +08:00
|
|
|
if (acpi_dock_match(handle))
|
2006-07-10 05:22:28 +08:00
|
|
|
return 1;
|
2009-10-20 05:14:50 +08:00
|
|
|
|
|
|
|
list_for_each_entry(dock_station, &dock_stations, sibling)
|
2008-08-28 10:03:58 +08:00
|
|
|
if (find_dock_dependent_device(dock_station, handle))
|
|
|
|
return 1;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(is_dock_device);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dock_present - see if the dock station is present.
|
|
|
|
* @ds: the dock station
|
|
|
|
*
|
|
|
|
* execute the _STA method. note that present does not
|
|
|
|
* imply that we are docked.
|
|
|
|
*/
|
|
|
|
static int dock_present(struct dock_station *ds)
|
|
|
|
{
|
2008-10-10 14:22:59 +08:00
|
|
|
unsigned long long sta;
|
2006-07-10 05:22:28 +08:00
|
|
|
acpi_status status;
|
|
|
|
|
|
|
|
if (ds) {
|
|
|
|
status = acpi_evaluate_integer(ds->handle, "_STA", NULL, &sta);
|
|
|
|
if (ACPI_SUCCESS(status) && sta)
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dock_create_acpi_device - add new devices to acpi
|
|
|
|
* @handle - handle of the device to add
|
|
|
|
*
|
|
|
|
* This function will create a new acpi_device for the given
|
|
|
|
* handle if one does not exist already. This should cause
|
|
|
|
* acpi to scan for drivers for the given devices, and call
|
|
|
|
* matching driver's add routine.
|
|
|
|
*/
|
2013-06-29 00:24:37 +08:00
|
|
|
static void dock_create_acpi_device(acpi_handle handle)
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
ACPI / scan: Add acpi_device objects for all device nodes in the namespace
Modify the ACPI namespace scanning code to register a struct
acpi_device object for every namespace node representing a device,
processor and so on, even if the device represented by that namespace
node is reported to be not present and not functional by _STA.
There are multiple reasons to do that. First of all, it avoids
quite a lot of overhead when struct acpi_device objects are
deleted every time acpi_bus_trim() is run and then added again
by a subsequent acpi_bus_scan() for the same scope, although the
namespace objects they correspond to stay in memory all the time
(which always is the case on a vast majority of systems).
Second, it will allow user space to see that there are namespace
nodes representing devices that are not present at the moment and may
be added to the system. It will also allow user space to evaluate
_SUN for those nodes to check what physical slots the "missing"
devices may be put into and it will make sense to add a sysfs
attribute for _STA evaluation after this change (that will be
useful for thermal management on some systems).
Next, it will help to consolidate the ACPI hotplug handling among
subsystems by making it possible to store hotplug-related information
in struct acpi_device objects in a standard common way.
Finally, it will help to avoid a race condition related to the
deletion of ACPI namespace nodes. Namely, namespace nodes may be
deleted as a result of a table unload triggered by _EJ0 or _DCK.
If a hotplug notification for one of those nodes is triggered
right before the deletion and it executes a hotplug callback
via acpi_hotplug_execute(), the ACPI handle passed to that
callback may be stale when the callback actually runs. One way
to work around that is to always pass struct acpi_device pointers
to hotplug callbacks after doing a get_device() on the objects in
question which eliminates the use-after-free possibility (the ACPI
handles in those objects are invalidated by acpi_scan_drop_device(),
so they will trigger ACPICA errors on attempts to use them).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-23 04:54:37 +08:00
|
|
|
struct acpi_device *device = NULL;
|
2006-07-10 05:22:28 +08:00
|
|
|
int ret;
|
|
|
|
|
ACPI / scan: Add acpi_device objects for all device nodes in the namespace
Modify the ACPI namespace scanning code to register a struct
acpi_device object for every namespace node representing a device,
processor and so on, even if the device represented by that namespace
node is reported to be not present and not functional by _STA.
There are multiple reasons to do that. First of all, it avoids
quite a lot of overhead when struct acpi_device objects are
deleted every time acpi_bus_trim() is run and then added again
by a subsequent acpi_bus_scan() for the same scope, although the
namespace objects they correspond to stay in memory all the time
(which always is the case on a vast majority of systems).
Second, it will allow user space to see that there are namespace
nodes representing devices that are not present at the moment and may
be added to the system. It will also allow user space to evaluate
_SUN for those nodes to check what physical slots the "missing"
devices may be put into and it will make sense to add a sysfs
attribute for _STA evaluation after this change (that will be
useful for thermal management on some systems).
Next, it will help to consolidate the ACPI hotplug handling among
subsystems by making it possible to store hotplug-related information
in struct acpi_device objects in a standard common way.
Finally, it will help to avoid a race condition related to the
deletion of ACPI namespace nodes. Namely, namespace nodes may be
deleted as a result of a table unload triggered by _EJ0 or _DCK.
If a hotplug notification for one of those nodes is triggered
right before the deletion and it executes a hotplug callback
via acpi_hotplug_execute(), the ACPI handle passed to that
callback may be stale when the callback actually runs. One way
to work around that is to always pass struct acpi_device pointers
to hotplug callbacks after doing a get_device() on the objects in
question which eliminates the use-after-free possibility (the ACPI
handles in those objects are invalidated by acpi_scan_drop_device(),
so they will trigger ACPICA errors on attempts to use them).
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-23 04:54:37 +08:00
|
|
|
acpi_bus_get_device(handle, &device);
|
|
|
|
if (!acpi_device_enumerated(device)) {
|
2013-01-19 08:27:35 +08:00
|
|
|
ret = acpi_bus_scan(handle);
|
2012-12-21 07:36:47 +08:00
|
|
|
if (ret)
|
2009-10-20 05:14:50 +08:00
|
|
|
pr_debug("error adding bus, %x\n", -ret);
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* dock_remove_acpi_device - remove the acpi_device struct from acpi
|
|
|
|
* @handle - the handle of the device to remove
|
|
|
|
*
|
|
|
|
* Tell acpi to remove the acpi_device. This should cause any loaded
|
|
|
|
* driver to have it's remove routine called.
|
|
|
|
*/
|
|
|
|
static void dock_remove_acpi_device(acpi_handle handle)
|
|
|
|
{
|
|
|
|
struct acpi_device *device;
|
|
|
|
|
2013-01-26 07:27:44 +08:00
|
|
|
if (!acpi_bus_get_device(handle, &device))
|
|
|
|
acpi_bus_trim(device);
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2013-07-01 05:46:42 +08:00
|
|
|
* hot_remove_dock_devices - Remove dock station devices.
|
|
|
|
* @ds: Dock station.
|
|
|
|
*/
|
|
|
|
static void hot_remove_dock_devices(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
struct dock_dependent_device *dd;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Walk the list in reverse order so that devices that have been added
|
|
|
|
* last are removed first (in case there are some indirect dependencies
|
|
|
|
* between them).
|
|
|
|
*/
|
|
|
|
list_for_each_entry_reverse(dd, &ds->dependent_devices, list)
|
|
|
|
dock_hotplug_event(dd, ACPI_NOTIFY_EJECT_REQUEST, false);
|
|
|
|
|
|
|
|
list_for_each_entry_reverse(dd, &ds->dependent_devices, list)
|
|
|
|
dock_remove_acpi_device(dd->handle);
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* hotplug_dock_devices - Insert devices on a dock station.
|
2006-07-10 05:22:28 +08:00
|
|
|
* @ds: the dock station
|
2013-07-01 05:46:42 +08:00
|
|
|
* @event: either bus check or device check request
|
2006-07-10 05:22:28 +08:00
|
|
|
*
|
|
|
|
* Some devices on the dock station need to have drivers called
|
|
|
|
* to perform hotplug operations after a dock event has occurred.
|
|
|
|
* Traverse the list of dock devices that have registered a
|
|
|
|
* hotplug handler, and call the handler.
|
|
|
|
*/
|
|
|
|
static void hotplug_dock_devices(struct dock_station *ds, u32 event)
|
|
|
|
{
|
|
|
|
struct dock_dependent_device *dd;
|
|
|
|
|
2013-07-05 09:03:25 +08:00
|
|
|
/* Call driver specific post-dock fixups. */
|
|
|
|
list_for_each_entry(dd, &ds->dependent_devices, list)
|
|
|
|
dock_hotplug_event(dd, event, DOCK_CALL_FIXUP);
|
|
|
|
|
2013-07-01 05:46:42 +08:00
|
|
|
/* Call driver specific hotplug functions. */
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
list_for_each_entry(dd, &ds->dependent_devices, list)
|
2013-07-05 09:03:25 +08:00
|
|
|
dock_hotplug_event(dd, event, DOCK_CALL_HANDLER);
|
2006-07-10 05:22:28 +08:00
|
|
|
|
|
|
|
/*
|
2013-07-01 05:46:42 +08:00
|
|
|
* Now make sure that an acpi_device is created for each dependent
|
|
|
|
* device. That will cause scan handlers to be attached to device
|
|
|
|
* objects or acpi_drivers to be stopped/started if they are present.
|
2006-07-10 05:22:28 +08:00
|
|
|
*/
|
2013-07-01 05:46:42 +08:00
|
|
|
list_for_each_entry(dd, &ds->dependent_devices, list)
|
|
|
|
dock_create_acpi_device(dd->handle);
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static void dock_event(struct dock_station *ds, u32 event, int num)
|
|
|
|
{
|
2008-08-28 10:03:58 +08:00
|
|
|
struct device *dev = &ds->dock_device->dev;
|
2007-08-11 04:10:32 +08:00
|
|
|
char event_string[13];
|
2007-05-10 06:10:22 +08:00
|
|
|
char *envp[] = { event_string, NULL };
|
2008-08-28 10:06:16 +08:00
|
|
|
struct dock_dependent_device *dd;
|
2007-05-10 06:10:22 +08:00
|
|
|
|
|
|
|
if (num == UNDOCK_EVENT)
|
2007-08-11 04:10:32 +08:00
|
|
|
sprintf(event_string, "EVENT=undock");
|
2007-05-10 06:10:22 +08:00
|
|
|
else
|
2007-08-11 04:10:32 +08:00
|
|
|
sprintf(event_string, "EVENT=dock");
|
2007-05-10 06:10:22 +08:00
|
|
|
|
2006-08-02 05:59:19 +08:00
|
|
|
/*
|
2006-12-12 04:05:08 +08:00
|
|
|
* Indicate that the status of the dock station has
|
|
|
|
* changed.
|
2006-08-02 05:59:19 +08:00
|
|
|
*/
|
2008-08-28 10:06:16 +08:00
|
|
|
if (num == DOCK_EVENT)
|
|
|
|
kobject_uevent_env(&dev->kobj, KOBJ_CHANGE, envp);
|
|
|
|
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
list_for_each_entry(dd, &ds->dependent_devices, list)
|
2013-07-05 09:03:25 +08:00
|
|
|
dock_hotplug_event(dd, event, DOCK_CALL_UEVENT);
|
2009-10-20 05:14:50 +08:00
|
|
|
|
2008-08-28 10:06:16 +08:00
|
|
|
if (num != DOCK_EVENT)
|
|
|
|
kobject_uevent_env(&dev->kobj, KOBJ_CHANGE, envp);
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* handle_dock - handle a dock event
|
|
|
|
* @ds: the dock station
|
|
|
|
* @dock: to dock, or undock - that is the question
|
|
|
|
*
|
|
|
|
* Execute the _DCK method in response to an acpi event
|
|
|
|
*/
|
|
|
|
static void handle_dock(struct dock_station *ds, int dock)
|
|
|
|
{
|
|
|
|
acpi_status status;
|
|
|
|
struct acpi_object_list arg_list;
|
|
|
|
union acpi_object arg;
|
2013-09-03 08:32:10 +08:00
|
|
|
unsigned long long value;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2012-11-21 07:42:30 +08:00
|
|
|
acpi_handle_info(ds->handle, "%s\n", dock ? "docking" : "undocking");
|
2006-07-10 05:22:28 +08:00
|
|
|
|
|
|
|
/* _DCK method has one argument */
|
|
|
|
arg_list.count = 1;
|
|
|
|
arg_list.pointer = &arg;
|
|
|
|
arg.type = ACPI_TYPE_INTEGER;
|
|
|
|
arg.integer.value = dock;
|
2013-09-03 08:32:10 +08:00
|
|
|
status = acpi_evaluate_integer(ds->handle, "_DCK", &arg_list, &value);
|
2008-08-28 10:03:58 +08:00
|
|
|
if (ACPI_FAILURE(status) && status != AE_NOT_FOUND)
|
2012-11-21 07:42:30 +08:00
|
|
|
acpi_handle_err(ds->handle, "Failed to execute _DCK (0x%x)\n",
|
|
|
|
status);
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
static inline void dock(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
handle_dock(ds, 1);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline void undock(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
handle_dock(ds, 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline void begin_dock(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
ds->flags |= DOCK_DOCKING;
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline void complete_dock(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
ds->flags &= ~(DOCK_DOCKING);
|
|
|
|
ds->last_dock_time = jiffies;
|
|
|
|
}
|
|
|
|
|
2007-05-10 06:08:15 +08:00
|
|
|
static inline void begin_undock(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
ds->flags |= DOCK_UNDOCKING;
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline void complete_undock(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
ds->flags &= ~(DOCK_UNDOCKING);
|
|
|
|
}
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
/**
|
|
|
|
* dock_in_progress - see if we are in the middle of handling a dock event
|
|
|
|
* @ds: the dock station
|
|
|
|
*
|
|
|
|
* Sometimes while docking, false dock events can be sent to the driver
|
|
|
|
* because good connections aren't made or some other reason. Ignore these
|
|
|
|
* if we are in the middle of doing something.
|
|
|
|
*/
|
|
|
|
static int dock_in_progress(struct dock_station *ds)
|
|
|
|
{
|
|
|
|
if ((ds->flags & DOCK_DOCKING) ||
|
|
|
|
time_before(jiffies, (ds->last_dock_time + HZ)))
|
|
|
|
return 1;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
|
|
|
* register_hotplug_dock_device - register a hotplug function
|
|
|
|
* @handle: the handle of the device
|
2008-08-28 10:06:16 +08:00
|
|
|
* @ops: handlers to call after docking
|
2006-07-10 05:22:28 +08:00
|
|
|
* @context: device specific data
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
* @init: Optional initialization routine to run after registration
|
|
|
|
* @release: Optional release routine to run on unregistration
|
2006-07-10 05:22:28 +08:00
|
|
|
*
|
|
|
|
* If a driver would like to perform a hotplug operation after a dock
|
|
|
|
* event, they can register an acpi_notifiy_handler to be called by
|
|
|
|
* the dock driver after _DCK is executed.
|
|
|
|
*/
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
int register_hotplug_dock_device(acpi_handle handle,
|
|
|
|
const struct acpi_dock_ops *ops, void *context,
|
|
|
|
void (*init)(void *), void (*release)(void *))
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
|
|
|
struct dock_dependent_device *dd;
|
2008-08-28 10:03:58 +08:00
|
|
|
struct dock_station *dock_station;
|
2008-08-28 10:07:14 +08:00
|
|
|
int ret = -EINVAL;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
if (WARN_ON(!context))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2008-08-28 10:03:58 +08:00
|
|
|
if (!dock_station_count)
|
2006-07-10 05:22:28 +08:00
|
|
|
return -ENODEV;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* make sure this handle is for a device dependent on the dock,
|
|
|
|
* this would include the dock station itself
|
|
|
|
*/
|
2009-10-02 01:59:23 +08:00
|
|
|
list_for_each_entry(dock_station, &dock_stations, sibling) {
|
2008-08-28 10:07:14 +08:00
|
|
|
/*
|
|
|
|
* An ATA bay can be in a dock and itself can be ejected
|
tree-wide: Assorted spelling fixes
In particular, several occurances of funny versions of 'success',
'unknown', 'therefore', 'acknowledge', 'argument', 'achieve', 'address',
'beginning', 'desirable', 'separate' and 'necessary' are fixed.
Signed-off-by: Daniel Mack <daniel@caiaq.de>
Cc: Joe Perches <joe@perches.com>
Cc: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
2010-02-03 08:01:28 +08:00
|
|
|
* separately, so there are two 'dock stations' which need the
|
2008-08-28 10:07:14 +08:00
|
|
|
* ops
|
|
|
|
*/
|
2008-08-28 10:03:58 +08:00
|
|
|
dd = find_dock_dependent_device(dock_station, handle);
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
if (dd && !dock_init_hotplug(dd, ops, context, init, release))
|
2008-08-28 10:07:14 +08:00
|
|
|
ret = 0;
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
2008-08-28 10:07:14 +08:00
|
|
|
return ret;
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(register_hotplug_dock_device);
|
|
|
|
|
|
|
|
/**
|
|
|
|
* unregister_hotplug_dock_device - remove yourself from the hotplug list
|
|
|
|
* @handle: the acpi handle of the device
|
|
|
|
*/
|
|
|
|
void unregister_hotplug_dock_device(acpi_handle handle)
|
|
|
|
{
|
|
|
|
struct dock_dependent_device *dd;
|
2008-08-28 10:03:58 +08:00
|
|
|
struct dock_station *dock_station;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2008-08-28 10:03:58 +08:00
|
|
|
if (!dock_station_count)
|
2006-07-10 05:22:28 +08:00
|
|
|
return;
|
|
|
|
|
2009-10-02 01:59:23 +08:00
|
|
|
list_for_each_entry(dock_station, &dock_stations, sibling) {
|
2008-08-28 10:03:58 +08:00
|
|
|
dd = find_dock_dependent_device(dock_station, handle);
|
|
|
|
if (dd)
|
ACPI / dock / PCI: Synchronous handling of dock events for PCI devices
The interactions between the ACPI dock driver and the ACPI-based PCI
hotplug (acpiphp) are currently problematic because of ordering
issues during hot-remove operations.
First of all, the current ACPI glue code expects that physical
devices will always be deleted before deleting the companion ACPI
device objects. Otherwise, acpi_unbind_one() will fail with a
warning message printed to the kernel log, for example:
[ 185.026073] usb usb5: Oops, 'acpi_handle' corrupt
[ 185.035150] pci 0000:1b:00.0: Oops, 'acpi_handle' corrupt
[ 185.035515] pci 0000:18:02.0: Oops, 'acpi_handle' corrupt
[ 180.013656] port1: Oops, 'acpi_handle' corrupt
This means, in particular, that struct pci_dev objects have to
be deleted before the struct acpi_device objects they are "glued"
with.
Now, the following happens the during the undocking of an ACPI-based
dock station:
1) hotplug_dock_devices() invokes registered hotplug callbacks to
destroy physical devices associated with the ACPI device objects
depending on the dock station. It calls dd->ops->handler() for
each of those device objects.
2) For PCI devices dd->ops->handler() points to
handle_hotplug_event_func() that queues up a separate work item
to execute _handle_hotplug_event_func() for the given device and
returns immediately. That work item will be executed later.
3) hotplug_dock_devices() calls dock_remove_acpi_device() for each
device depending on the dock station. This runs acpi_bus_trim()
for each of them, which causes the underlying ACPI device object
to be destroyed, but the work items queued up by
handle_hotplug_event_func() haven't been started yet.
4) _handle_hotplug_event_func() queued up in step 2) are executed
and cause the above failure to happen, because the PCI devices
they handle do not have the companion ACPI device objects any
more (those objects have been deleted in step 3).
The possible breakage doesn't end here, though, because
hotplug_dock_devices() may return before at least some of the
_handle_hotplug_event_func() work items spawned by it have a
chance to complete and then undock() will cause _DCK to be
evaluated and that will cause the devices handled by the
_handle_hotplug_event_func() to go away possibly while they are
being accessed.
This means that dd->ops->handler() for PCI devices should not point
to handle_hotplug_event_func(). Instead, it should point to a
function that will do the work of _handle_hotplug_event_func()
synchronously. For this reason, introduce such a function,
hotplug_event_func(), and modity acpiphp_dock_ops to point to
it as the handler.
Unfortunately, however, this is not sufficient, because if the dock
code were not changed further, hotplug_event_func() would now
deadlock with hotplug_dock_devices() that called it, since it would
run unregister_hotplug_dock_device() which in turn would attempt to
acquire the dock station's hp_lock mutex already acquired by
hotplug_dock_devices().
To resolve that deadlock use the observation that
unregister_hotplug_dock_device() won't need to acquire hp_lock
if PCI bridges the devices on the dock station depend on are
prevented from being removed prematurely while the first loop in
hotplug_dock_devices() is in progress.
To make that possible, introduce a mechanism by which the callers of
register_hotplug_dock_device() can provide "init" and "release"
routines that will be executed, respectively, during the addition
and removal of the physical device object associated with the
given ACPI device handle. Make acpiphp use two new functions,
acpiphp_dock_init() and acpiphp_dock_release(), that call
get_bridge() and put_bridge(), respectively, on the acpiphp bridge
holding the given device, for this purpose.
In addition to that, remove the dock station's list of
"hotplug devices" and make the dock code always walk the whole list
of "dependent devices" instead in such a way that the loops in
hotplug_dock_devices() and dock_event() (replacing the loops over
"hotplug devices") will take references to the list entries that
register_hotplug_dock_device() has been called for. That prevents
the "release" routines associated with those entries from being
called while the given entry is being processed and for PCI
devices this means that their bridges won't be removed (by a
concurrent thread) while hotplug_event_func() handling them is
being executed.
This change is based on two earlier patches from Jiang Liu.
References: https://bugzilla.kernel.org/show_bug.cgi?id=59501
Reported-and-tested-by: Alexander E. Patrakov <patrakov@gmail.com>
Tracked-down-by: Jiang Liu <jiang.liu@huawei.com>
Tested-by: Illya Klymov <xanf@xanf.me>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: 3.9+ <stable@vger.kernel.org>
2013-06-24 17:22:53 +08:00
|
|
|
dock_release_hotplug(dd);
|
2008-08-28 10:03:58 +08:00
|
|
|
}
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(unregister_hotplug_dock_device);
|
|
|
|
|
2006-12-05 06:49:58 +08:00
|
|
|
/**
|
|
|
|
* handle_eject_request - handle an undock request checking for error conditions
|
|
|
|
*
|
|
|
|
* Check to make sure the dock device is still present, then undock and
|
|
|
|
* hotremove all the devices that may need removing.
|
|
|
|
*/
|
|
|
|
static int handle_eject_request(struct dock_station *ds, u32 event)
|
|
|
|
{
|
|
|
|
if (dock_in_progress(ds))
|
|
|
|
return -EBUSY;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* here we need to generate the undock
|
|
|
|
* event prior to actually doing the undock
|
|
|
|
* so that the device struct still exists.
|
2008-08-06 23:56:01 +08:00
|
|
|
* Also, even send the dock event if the
|
|
|
|
* device is not present anymore
|
2006-12-05 06:49:58 +08:00
|
|
|
*/
|
|
|
|
dock_event(ds, event, UNDOCK_EVENT);
|
2008-08-06 23:56:01 +08:00
|
|
|
|
2013-07-01 05:46:42 +08:00
|
|
|
hot_remove_dock_devices(ds);
|
2006-12-05 06:49:58 +08:00
|
|
|
undock(ds);
|
2013-06-29 00:24:42 +08:00
|
|
|
acpi_evaluate_lck(ds->handle, 0);
|
|
|
|
acpi_evaluate_ej0(ds->handle);
|
2006-12-05 06:49:58 +08:00
|
|
|
if (dock_present(ds)) {
|
2012-11-21 07:42:30 +08:00
|
|
|
acpi_handle_err(ds->handle, "Unable to undock!\n");
|
2006-12-05 06:49:58 +08:00
|
|
|
return -EBUSY;
|
|
|
|
}
|
2007-05-10 06:08:15 +08:00
|
|
|
complete_undock(ds);
|
2006-12-05 06:49:58 +08:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
/**
|
|
|
|
* dock_notify - act upon an acpi dock notification
|
2013-07-01 05:48:49 +08:00
|
|
|
* @ds: dock station
|
2006-07-10 05:22:28 +08:00
|
|
|
* @event: the acpi event
|
|
|
|
*
|
|
|
|
* If we are notified to dock, then check to see if the dock is
|
|
|
|
* present and then dock. Notify all drivers of the dock event,
|
2006-12-05 06:49:58 +08:00
|
|
|
* and then hotplug and devices that may need hotplugging.
|
2006-07-10 05:22:28 +08:00
|
|
|
*/
|
2013-07-01 05:48:49 +08:00
|
|
|
static void dock_notify(struct dock_station *ds, u32 event)
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
2013-07-01 05:48:49 +08:00
|
|
|
acpi_handle handle = ds->handle;
|
|
|
|
struct acpi_device *ad;
|
2008-08-28 10:03:58 +08:00
|
|
|
int surprise_removal = 0;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2008-08-28 10:03:58 +08:00
|
|
|
/*
|
|
|
|
* According to acpi spec 3.0a, if a DEVICE_CHECK notification
|
|
|
|
* is sent and _DCK is present, it is assumed to mean an undock
|
|
|
|
* request.
|
|
|
|
*/
|
|
|
|
if ((ds->flags & DOCK_IS_DOCK) && event == ACPI_NOTIFY_DEVICE_CHECK)
|
|
|
|
event = ACPI_NOTIFY_EJECT_REQUEST;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* dock station: BUS_CHECK - docked or surprise removal
|
|
|
|
* DEVICE_CHECK - undocked
|
|
|
|
* other device: BUS_CHECK/DEVICE_CHECK - added or surprise removal
|
|
|
|
*
|
|
|
|
* To simplify event handling, dock dependent device handler always
|
|
|
|
* get ACPI_NOTIFY_BUS_CHECK/ACPI_NOTIFY_DEVICE_CHECK for add and
|
|
|
|
* ACPI_NOTIFY_EJECT_REQUEST for removal
|
|
|
|
*/
|
2006-07-10 05:22:28 +08:00
|
|
|
switch (event) {
|
|
|
|
case ACPI_NOTIFY_BUS_CHECK:
|
2008-08-28 10:03:58 +08:00
|
|
|
case ACPI_NOTIFY_DEVICE_CHECK:
|
2013-07-01 05:48:49 +08:00
|
|
|
if (!dock_in_progress(ds) && acpi_bus_get_device(handle, &ad)) {
|
2006-07-10 05:22:28 +08:00
|
|
|
begin_dock(ds);
|
|
|
|
dock(ds);
|
|
|
|
if (!dock_present(ds)) {
|
2012-11-21 07:42:30 +08:00
|
|
|
acpi_handle_err(handle, "Unable to dock!\n");
|
2008-08-28 10:02:03 +08:00
|
|
|
complete_dock(ds);
|
2006-07-10 05:22:28 +08:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
hotplug_dock_devices(ds, event);
|
|
|
|
complete_dock(ds);
|
|
|
|
dock_event(ds, event, DOCK_EVENT);
|
2013-06-29 00:24:42 +08:00
|
|
|
acpi_evaluate_lck(ds->handle, 1);
|
2010-12-13 13:36:15 +08:00
|
|
|
acpi_update_all_gpes();
|
2008-08-28 10:03:58 +08:00
|
|
|
break;
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
2008-08-28 10:03:58 +08:00
|
|
|
if (dock_present(ds) || dock_in_progress(ds))
|
|
|
|
break;
|
|
|
|
/* This is a surprise removal */
|
|
|
|
surprise_removal = 1;
|
|
|
|
event = ACPI_NOTIFY_EJECT_REQUEST;
|
|
|
|
/* Fall back */
|
2006-07-10 05:22:28 +08:00
|
|
|
case ACPI_NOTIFY_EJECT_REQUEST:
|
2007-05-10 06:08:15 +08:00
|
|
|
begin_undock(ds);
|
2008-08-28 10:05:45 +08:00
|
|
|
if ((immediate_undock && !(ds->flags & DOCK_IS_ATA))
|
|
|
|
|| surprise_removal)
|
2007-05-10 06:08:15 +08:00
|
|
|
handle_eject_request(ds, event);
|
|
|
|
else
|
|
|
|
dock_event(ds, event, UNDOCK_EVENT);
|
2006-07-10 05:22:28 +08:00
|
|
|
break;
|
|
|
|
default:
|
2012-11-21 07:42:30 +08:00
|
|
|
acpi_handle_err(handle, "Unknown dock event %d\n", event);
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 08:45:40 +08:00
|
|
|
static void acpi_dock_deferred_cb(void *data, u32 event)
|
2008-08-28 10:05:06 +08:00
|
|
|
{
|
ACPI / hotplug: Fix concurrency issues and memory leaks
This changeset is aimed at fixing a few different but related
problems in the ACPI hotplug infrastructure.
First of all, since notify handlers may be run in parallel with
acpi_bus_scan(), acpi_bus_trim() and acpi_bus_hot_remove_device()
and some of them are installed for ACPI handles that have no struct
acpi_device objects attached (i.e. before those objects are created),
those notify handlers have to take acpi_scan_lock to prevent races
from taking place (e.g. a struct acpi_device is found to be present
for the given ACPI handle, but right after that it is removed by
acpi_bus_trim() running in parallel to the given notify handler).
Moreover, since some of them call acpi_bus_scan() and
acpi_bus_trim(), this leads to the conclusion that acpi_scan_lock
should be acquired by the callers of these two funtions rather by
these functions themselves.
For these reasons, make all notify handlers that can handle device
addition and eject events take acpi_scan_lock and remove the
acpi_scan_lock locking from acpi_bus_scan() and acpi_bus_trim().
Accordingly, update all of their users to make sure that they
are always called under acpi_scan_lock.
Furthermore, since eject operations are carried out asynchronously
with respect to the notify events that trigger them, with the help
of acpi_bus_hot_remove_device(), even if notify handlers take the
ACPI scan lock, it still is possible that, for example,
acpi_bus_trim() will run between acpi_bus_hot_remove_device() and
the notify handler that scheduled its execution and that
acpi_bus_trim() will remove the device node passed to
acpi_bus_hot_remove_device() for ejection. In that case, the struct
acpi_device object obtained by acpi_bus_hot_remove_device() will be
invalid and not-so-funny things will ensue. To protect agaist that,
make the users of acpi_bus_hot_remove_device() run get_device() on
ACPI device node objects that are about to be passed to it and make
acpi_bus_hot_remove_device() run put_device() on them and check if
their ACPI handles are not NULL (make acpi_device_unregister() clear
the device nodes' ACPI handles for that check to work).
Finally, observe that acpi_os_hotplug_execute() actually can fail,
in which case its caller ought to free memory allocated for the
context object to prevent leaks from happening. It also needs to
run put_device() on the device node that it ran get_device() on
previously in that case. Modify the code accordingly.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
2013-02-13 21:36:47 +08:00
|
|
|
acpi_scan_lock_acquire();
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 08:45:40 +08:00
|
|
|
dock_notify(data, event);
|
ACPI / hotplug: Fix concurrency issues and memory leaks
This changeset is aimed at fixing a few different but related
problems in the ACPI hotplug infrastructure.
First of all, since notify handlers may be run in parallel with
acpi_bus_scan(), acpi_bus_trim() and acpi_bus_hot_remove_device()
and some of them are installed for ACPI handles that have no struct
acpi_device objects attached (i.e. before those objects are created),
those notify handlers have to take acpi_scan_lock to prevent races
from taking place (e.g. a struct acpi_device is found to be present
for the given ACPI handle, but right after that it is removed by
acpi_bus_trim() running in parallel to the given notify handler).
Moreover, since some of them call acpi_bus_scan() and
acpi_bus_trim(), this leads to the conclusion that acpi_scan_lock
should be acquired by the callers of these two funtions rather by
these functions themselves.
For these reasons, make all notify handlers that can handle device
addition and eject events take acpi_scan_lock and remove the
acpi_scan_lock locking from acpi_bus_scan() and acpi_bus_trim().
Accordingly, update all of their users to make sure that they
are always called under acpi_scan_lock.
Furthermore, since eject operations are carried out asynchronously
with respect to the notify events that trigger them, with the help
of acpi_bus_hot_remove_device(), even if notify handlers take the
ACPI scan lock, it still is possible that, for example,
acpi_bus_trim() will run between acpi_bus_hot_remove_device() and
the notify handler that scheduled its execution and that
acpi_bus_trim() will remove the device node passed to
acpi_bus_hot_remove_device() for ejection. In that case, the struct
acpi_device object obtained by acpi_bus_hot_remove_device() will be
invalid and not-so-funny things will ensue. To protect agaist that,
make the users of acpi_bus_hot_remove_device() run get_device() on
ACPI device node objects that are about to be passed to it and make
acpi_bus_hot_remove_device() run put_device() on them and check if
their ACPI handles are not NULL (make acpi_device_unregister() clear
the device nodes' ACPI handles for that check to work).
Finally, observe that acpi_os_hotplug_execute() actually can fail,
in which case its caller ought to free memory allocated for the
context object to prevent leaks from happening. It also needs to
run put_device() on the device node that it ran get_device() on
previously in that case. Modify the code accordingly.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
2013-02-13 21:36:47 +08:00
|
|
|
acpi_scan_lock_release();
|
2008-08-28 10:05:06 +08:00
|
|
|
}
|
|
|
|
|
2013-07-01 05:48:49 +08:00
|
|
|
static void dock_notify_handler(acpi_handle handle, u32 event, void *data)
|
2008-08-28 10:04:29 +08:00
|
|
|
{
|
|
|
|
if (event != ACPI_NOTIFY_BUS_CHECK && event != ACPI_NOTIFY_DEVICE_CHECK
|
|
|
|
&& event != ACPI_NOTIFY_EJECT_REQUEST)
|
2013-07-01 05:48:49 +08:00
|
|
|
return;
|
ACPI / hotplug: Fix concurrency issues and memory leaks
This changeset is aimed at fixing a few different but related
problems in the ACPI hotplug infrastructure.
First of all, since notify handlers may be run in parallel with
acpi_bus_scan(), acpi_bus_trim() and acpi_bus_hot_remove_device()
and some of them are installed for ACPI handles that have no struct
acpi_device objects attached (i.e. before those objects are created),
those notify handlers have to take acpi_scan_lock to prevent races
from taking place (e.g. a struct acpi_device is found to be present
for the given ACPI handle, but right after that it is removed by
acpi_bus_trim() running in parallel to the given notify handler).
Moreover, since some of them call acpi_bus_scan() and
acpi_bus_trim(), this leads to the conclusion that acpi_scan_lock
should be acquired by the callers of these two funtions rather by
these functions themselves.
For these reasons, make all notify handlers that can handle device
addition and eject events take acpi_scan_lock and remove the
acpi_scan_lock locking from acpi_bus_scan() and acpi_bus_trim().
Accordingly, update all of their users to make sure that they
are always called under acpi_scan_lock.
Furthermore, since eject operations are carried out asynchronously
with respect to the notify events that trigger them, with the help
of acpi_bus_hot_remove_device(), even if notify handlers take the
ACPI scan lock, it still is possible that, for example,
acpi_bus_trim() will run between acpi_bus_hot_remove_device() and
the notify handler that scheduled its execution and that
acpi_bus_trim() will remove the device node passed to
acpi_bus_hot_remove_device() for ejection. In that case, the struct
acpi_device object obtained by acpi_bus_hot_remove_device() will be
invalid and not-so-funny things will ensue. To protect agaist that,
make the users of acpi_bus_hot_remove_device() run get_device() on
ACPI device node objects that are about to be passed to it and make
acpi_bus_hot_remove_device() run put_device() on them and check if
their ACPI handles are not NULL (make acpi_device_unregister() clear
the device nodes' ACPI handles for that check to work).
Finally, observe that acpi_os_hotplug_execute() actually can fail,
in which case its caller ought to free memory allocated for the
context object to prevent leaks from happening. It also needs to
run put_device() on the device node that it ran get_device() on
previously in that case. Modify the code accordingly.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
2013-02-13 21:36:47 +08:00
|
|
|
|
ACPI / hotplug: Consolidate deferred execution of ACPI hotplug routines
There are two different interfaces for queuing up work items on the
ACPI hotplug workqueue, alloc_acpi_hp_work() used by PCI and PCI host
bridge hotplug code and acpi_os_hotplug_execute() used by the common
ACPI hotplug code and docking stations. They both are somewhat
cumbersome to use and work slightly differently.
The users of alloc_acpi_hp_work() have to submit a work function that
will extract the necessary data items from a struct acpi_hp_work
object allocated by alloc_acpi_hp_work() and then will free that
object, while it would be more straightforward to simply use a work
function with one more argument and let the interface take care of
the execution details.
The users of acpi_os_hotplug_execute() also have to deal with the
fact that it takes only one argument in addition to the work function
pointer, although acpi_os_execute_deferred() actually takes care of
the allocation and freeing of memory, so it would have been able to
pass more arguments to the work function if it hadn't been
constrained by the connection with acpi_os_execute().
Moreover, while alloc_acpi_hp_work() makes GFP_KERNEL memory
allocations, which is correct, because hotplug work items are
always queued up from process context, acpi_os_hotplug_execute()
uses GFP_ATOMIC, as that is needed by acpi_os_execute(). Also,
acpi_os_execute_deferred() queued up by it waits for the ACPI event
workqueues to flush before executing the work function, whereas
alloc_acpi_hp_work() can't do anything similar. That leads to
somewhat arbitrary differences in behavior between various ACPI
hotplug code paths and has to be straightened up.
For this reason, replace both alloc_acpi_hp_work() and
acpi_os_hotplug_execute() with a single interface,
acpi_hotplug_execute(), combining their behavior and being more
friendly to its users than any of the two.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Tested-by: Mika Westerberg <mika.westerberg@linux.intel.com>
2013-11-07 08:45:40 +08:00
|
|
|
acpi_hotplug_execute(acpi_dock_deferred_cb, data, event);
|
2008-08-28 10:04:29 +08:00
|
|
|
}
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
/**
|
|
|
|
* find_dock_devices - find devices on the dock station
|
|
|
|
* @handle: the handle of the device we are examining
|
|
|
|
* @lvl: unused
|
|
|
|
* @context: the dock station private data
|
|
|
|
* @rv: unused
|
|
|
|
*
|
|
|
|
* This function is called by acpi_walk_namespace. It will
|
|
|
|
* check to see if an object has an _EJD method. If it does, then it
|
|
|
|
* will see if it is dependent on the dock station.
|
|
|
|
*/
|
2013-07-01 05:46:02 +08:00
|
|
|
static acpi_status __init find_dock_devices(acpi_handle handle, u32 lvl,
|
|
|
|
void *context, void **rv)
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
2006-10-01 06:28:50 +08:00
|
|
|
struct dock_station *ds = context;
|
2013-07-01 05:46:02 +08:00
|
|
|
acpi_handle ejd = NULL;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2013-07-01 05:46:02 +08:00
|
|
|
acpi_bus_get_ejd(handle, &ejd);
|
|
|
|
if (ejd == ds->handle)
|
2009-10-20 05:14:29 +08:00
|
|
|
add_dock_dependent_device(ds, handle);
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
return AE_OK;
|
|
|
|
}
|
|
|
|
|
2006-12-05 06:49:58 +08:00
|
|
|
/*
|
|
|
|
* show_docked - read method for "docked" file in sysfs
|
|
|
|
*/
|
|
|
|
static ssize_t show_docked(struct device *dev,
|
|
|
|
struct device_attribute *attr, char *buf)
|
|
|
|
{
|
2009-01-20 19:18:24 +08:00
|
|
|
struct acpi_device *tmp;
|
|
|
|
|
2009-10-20 05:14:45 +08:00
|
|
|
struct dock_station *dock_station = dev->platform_data;
|
2006-12-05 06:49:58 +08:00
|
|
|
|
2013-01-31 11:23:53 +08:00
|
|
|
if (!acpi_bus_get_device(dock_station->handle, &tmp))
|
2009-01-20 19:18:24 +08:00
|
|
|
return snprintf(buf, PAGE_SIZE, "1\n");
|
|
|
|
return snprintf(buf, PAGE_SIZE, "0\n");
|
2006-12-05 06:49:58 +08:00
|
|
|
}
|
2007-10-25 00:24:42 +08:00
|
|
|
static DEVICE_ATTR(docked, S_IRUGO, show_docked, NULL);
|
2006-12-05 06:49:58 +08:00
|
|
|
|
2007-05-10 06:08:15 +08:00
|
|
|
/*
|
|
|
|
* show_flags - read method for flags file in sysfs
|
|
|
|
*/
|
|
|
|
static ssize_t show_flags(struct device *dev,
|
|
|
|
struct device_attribute *attr, char *buf)
|
|
|
|
{
|
2009-10-20 05:14:45 +08:00
|
|
|
struct dock_station *dock_station = dev->platform_data;
|
2007-05-10 06:08:15 +08:00
|
|
|
return snprintf(buf, PAGE_SIZE, "%d\n", dock_station->flags);
|
|
|
|
|
|
|
|
}
|
2007-10-25 00:24:42 +08:00
|
|
|
static DEVICE_ATTR(flags, S_IRUGO, show_flags, NULL);
|
2007-05-10 06:08:15 +08:00
|
|
|
|
2006-12-05 06:49:58 +08:00
|
|
|
/*
|
|
|
|
* write_undock - write method for "undock" file in sysfs
|
|
|
|
*/
|
|
|
|
static ssize_t write_undock(struct device *dev, struct device_attribute *attr,
|
|
|
|
const char *buf, size_t count)
|
|
|
|
{
|
|
|
|
int ret;
|
2009-10-20 05:14:45 +08:00
|
|
|
struct dock_station *dock_station = dev->platform_data;
|
2006-12-05 06:49:58 +08:00
|
|
|
|
|
|
|
if (!count)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2013-06-16 06:38:30 +08:00
|
|
|
acpi_scan_lock_acquire();
|
2008-03-12 08:07:27 +08:00
|
|
|
begin_undock(dock_station);
|
2006-12-05 06:49:58 +08:00
|
|
|
ret = handle_eject_request(dock_station, ACPI_NOTIFY_EJECT_REQUEST);
|
2013-06-16 06:38:30 +08:00
|
|
|
acpi_scan_lock_release();
|
2006-12-05 06:49:58 +08:00
|
|
|
return ret ? ret: count;
|
|
|
|
}
|
2007-10-25 00:24:42 +08:00
|
|
|
static DEVICE_ATTR(undock, S_IWUSR, NULL, write_undock);
|
2006-12-05 06:49:58 +08:00
|
|
|
|
2007-02-20 07:19:31 +08:00
|
|
|
/*
|
|
|
|
* show_dock_uid - read method for "uid" file in sysfs
|
|
|
|
*/
|
|
|
|
static ssize_t show_dock_uid(struct device *dev,
|
|
|
|
struct device_attribute *attr, char *buf)
|
|
|
|
{
|
2008-10-10 14:22:59 +08:00
|
|
|
unsigned long long lbuf;
|
2009-10-20 05:14:45 +08:00
|
|
|
struct dock_station *dock_station = dev->platform_data;
|
2007-05-10 06:04:24 +08:00
|
|
|
acpi_status status = acpi_evaluate_integer(dock_station->handle,
|
|
|
|
"_UID", NULL, &lbuf);
|
|
|
|
if (ACPI_FAILURE(status))
|
2007-02-20 07:19:31 +08:00
|
|
|
return 0;
|
2007-05-10 06:04:24 +08:00
|
|
|
|
2008-10-10 14:22:59 +08:00
|
|
|
return snprintf(buf, PAGE_SIZE, "%llx\n", lbuf);
|
2007-02-20 07:19:31 +08:00
|
|
|
}
|
2007-10-25 00:24:42 +08:00
|
|
|
static DEVICE_ATTR(uid, S_IRUGO, show_dock_uid, NULL);
|
2007-02-20 07:19:31 +08:00
|
|
|
|
2008-08-28 10:07:45 +08:00
|
|
|
static ssize_t show_dock_type(struct device *dev,
|
|
|
|
struct device_attribute *attr, char *buf)
|
|
|
|
{
|
2009-10-20 05:14:45 +08:00
|
|
|
struct dock_station *dock_station = dev->platform_data;
|
2008-08-28 10:07:45 +08:00
|
|
|
char *type;
|
|
|
|
|
|
|
|
if (dock_station->flags & DOCK_IS_DOCK)
|
|
|
|
type = "dock_station";
|
|
|
|
else if (dock_station->flags & DOCK_IS_ATA)
|
|
|
|
type = "ata_bay";
|
|
|
|
else if (dock_station->flags & DOCK_IS_BAT)
|
|
|
|
type = "battery_bay";
|
|
|
|
else
|
|
|
|
type = "unknown";
|
|
|
|
|
|
|
|
return snprintf(buf, PAGE_SIZE, "%s\n", type);
|
|
|
|
}
|
|
|
|
static DEVICE_ATTR(type, S_IRUGO, show_dock_type, NULL);
|
|
|
|
|
2009-10-20 05:14:24 +08:00
|
|
|
static struct attribute *dock_attributes[] = {
|
|
|
|
&dev_attr_docked.attr,
|
|
|
|
&dev_attr_flags.attr,
|
|
|
|
&dev_attr_undock.attr,
|
|
|
|
&dev_attr_uid.attr,
|
|
|
|
&dev_attr_type.attr,
|
|
|
|
NULL
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct attribute_group dock_attribute_group = {
|
|
|
|
.attrs = dock_attributes
|
|
|
|
};
|
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
/**
|
|
|
|
* dock_add - add a new dock station
|
|
|
|
* @handle: the dock station handle
|
|
|
|
*
|
|
|
|
* allocated and initialize a new dock station device. Find all devices
|
|
|
|
* that are on the dock station, and register for dock event notifications.
|
|
|
|
*/
|
2010-10-19 15:13:39 +08:00
|
|
|
static int __init dock_add(acpi_handle handle)
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
2013-07-05 09:23:36 +08:00
|
|
|
struct dock_station *dock_station, ds = { NULL, };
|
2009-10-20 05:14:50 +08:00
|
|
|
struct platform_device *dd;
|
2013-07-01 05:48:49 +08:00
|
|
|
acpi_status status;
|
2013-07-05 09:23:36 +08:00
|
|
|
int ret;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2013-07-05 09:23:36 +08:00
|
|
|
dd = platform_device_register_data(NULL, "dock", dock_station_count,
|
|
|
|
&ds, sizeof(ds));
|
2009-10-20 05:14:50 +08:00
|
|
|
if (IS_ERR(dd))
|
|
|
|
return PTR_ERR(dd);
|
|
|
|
|
|
|
|
dock_station = dd->dev.platform_data;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
|
|
|
dock_station->handle = handle;
|
2009-10-20 05:14:50 +08:00
|
|
|
dock_station->dock_device = dd;
|
2006-07-10 05:22:28 +08:00
|
|
|
dock_station->last_dock_time = jiffies - HZ;
|
2009-10-20 05:14:50 +08:00
|
|
|
|
|
|
|
INIT_LIST_HEAD(&dock_station->sibling);
|
|
|
|
INIT_LIST_HEAD(&dock_station->dependent_devices);
|
2007-05-10 06:08:15 +08:00
|
|
|
|
2007-05-10 06:09:12 +08:00
|
|
|
/* we want the dock device to send uevents */
|
2009-10-20 05:14:50 +08:00
|
|
|
dev_set_uevent_suppress(&dd->dev, 0);
|
2007-05-10 06:09:12 +08:00
|
|
|
|
2013-06-29 00:24:42 +08:00
|
|
|
if (acpi_dock_match(handle))
|
2008-08-28 10:03:58 +08:00
|
|
|
dock_station->flags |= DOCK_IS_DOCK;
|
2013-06-29 00:24:42 +08:00
|
|
|
if (acpi_ata_match(handle))
|
2008-08-28 10:03:58 +08:00
|
|
|
dock_station->flags |= DOCK_IS_ATA;
|
|
|
|
if (is_battery(handle))
|
|
|
|
dock_station->flags |= DOCK_IS_BAT;
|
|
|
|
|
2009-10-20 05:14:50 +08:00
|
|
|
ret = sysfs_create_group(&dd->dev.kobj, &dock_attribute_group);
|
2008-08-28 10:07:45 +08:00
|
|
|
if (ret)
|
2009-10-20 05:14:24 +08:00
|
|
|
goto err_unregister;
|
2006-12-05 06:49:43 +08:00
|
|
|
|
2006-07-10 05:22:28 +08:00
|
|
|
/* Find dependent devices */
|
|
|
|
acpi_walk_namespace(ACPI_TYPE_DEVICE, ACPI_ROOT_OBJECT,
|
2009-11-13 10:06:08 +08:00
|
|
|
ACPI_UINT32_MAX, find_dock_devices, NULL,
|
|
|
|
dock_station, NULL);
|
2006-07-10 05:22:28 +08:00
|
|
|
|
|
|
|
/* add the dock station as a device dependent on itself */
|
2009-10-20 05:14:29 +08:00
|
|
|
ret = add_dock_dependent_device(dock_station, handle);
|
|
|
|
if (ret)
|
2009-10-20 05:14:24 +08:00
|
|
|
goto err_rmgroup;
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2013-07-01 05:48:49 +08:00
|
|
|
status = acpi_install_notify_handler(handle, ACPI_SYSTEM_NOTIFY,
|
|
|
|
dock_notify_handler, dock_station);
|
2013-07-17 08:33:25 +08:00
|
|
|
if (ACPI_FAILURE(status)) {
|
|
|
|
ret = -ENODEV;
|
2013-07-01 05:48:49 +08:00
|
|
|
goto err_rmgroup;
|
2013-07-17 08:33:25 +08:00
|
|
|
}
|
2013-07-01 05:48:49 +08:00
|
|
|
|
2008-08-28 10:03:58 +08:00
|
|
|
dock_station_count++;
|
2009-10-02 01:59:23 +08:00
|
|
|
list_add(&dock_station->sibling, &dock_stations);
|
2006-07-10 05:22:28 +08:00
|
|
|
return 0;
|
|
|
|
|
2009-10-20 05:14:24 +08:00
|
|
|
err_rmgroup:
|
2013-07-01 05:50:24 +08:00
|
|
|
remove_dock_dependent_devices(dock_station);
|
2009-10-20 05:14:50 +08:00
|
|
|
sysfs_remove_group(&dd->dev.kobj, &dock_attribute_group);
|
2009-10-20 05:14:24 +08:00
|
|
|
err_unregister:
|
2009-10-20 05:14:50 +08:00
|
|
|
platform_device_unregister(dd);
|
2012-11-21 07:42:30 +08:00
|
|
|
acpi_handle_err(handle, "%s encountered error %d\n", __func__, ret);
|
2006-07-10 05:22:28 +08:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
/**
|
2012-10-23 07:30:26 +08:00
|
|
|
* find_dock_and_bay - look for dock stations and bays
|
2006-07-10 05:22:28 +08:00
|
|
|
* @handle: acpi handle of a device
|
|
|
|
* @lvl: unused
|
2012-10-23 07:30:26 +08:00
|
|
|
* @context: unused
|
2006-07-10 05:22:28 +08:00
|
|
|
* @rv: unused
|
|
|
|
*
|
2012-10-23 07:30:26 +08:00
|
|
|
* This is called by acpi_walk_namespace to look for dock stations and bays.
|
2006-07-10 05:22:28 +08:00
|
|
|
*/
|
2013-08-13 18:31:13 +08:00
|
|
|
static acpi_status __init
|
2012-10-23 07:30:26 +08:00
|
|
|
find_dock_and_bay(acpi_handle handle, u32 lvl, void *context, void **rv)
|
2006-07-10 05:22:28 +08:00
|
|
|
{
|
2013-06-29 00:24:42 +08:00
|
|
|
if (acpi_dock_match(handle) || is_ejectable_bay(handle))
|
2010-03-22 15:46:49 +08:00
|
|
|
dock_add(handle);
|
2009-10-20 05:14:50 +08:00
|
|
|
|
2010-03-22 15:46:49 +08:00
|
|
|
return AE_OK;
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|
|
|
|
|
2013-07-04 19:25:04 +08:00
|
|
|
void __init acpi_dock_init(void)
|
2008-08-28 10:03:58 +08:00
|
|
|
{
|
2012-10-23 07:30:26 +08:00
|
|
|
/* look for dock stations and bays */
|
2006-07-10 05:22:28 +08:00
|
|
|
acpi_walk_namespace(ACPI_TYPE_DEVICE, ACPI_ROOT_OBJECT,
|
2012-10-23 07:30:26 +08:00
|
|
|
ACPI_UINT32_MAX, find_dock_and_bay, NULL, NULL, NULL);
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2008-08-28 10:03:58 +08:00
|
|
|
if (!dock_station_count) {
|
2012-11-21 07:42:30 +08:00
|
|
|
pr_info(PREFIX "No dock devices found.\n");
|
2013-07-04 19:25:04 +08:00
|
|
|
return;
|
2008-08-28 10:03:58 +08:00
|
|
|
}
|
2006-07-10 05:22:28 +08:00
|
|
|
|
2012-11-21 07:42:30 +08:00
|
|
|
pr_info(PREFIX "%s: %d docks/bays found\n",
|
2008-08-28 10:03:58 +08:00
|
|
|
ACPI_DOCK_DRIVER_DESCRIPTION, dock_station_count);
|
2006-07-10 05:22:28 +08:00
|
|
|
}
|