Re: [PATCH] ACPI / dock: Take ACPI scan lock in write_undock()

2013-06-18 Thread Rafael J. Wysocki
On Tuesday, June 18, 2013 03:28:37 PM Toshi Kani wrote: > On Sun, 2013-06-16 at 00:16 +0200, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > Since commit 3757b94 (ACPI / hotplug: Fix concurrency issues and > > memory leaks) acpi_bus_scan() and acpi_bus_trim() must always be > > calle

Re: [PATCH] ACPI / dock: Take ACPI scan lock in write_undock()

2013-06-18 Thread Toshi Kani
On Sun, 2013-06-16 at 00:16 +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Since commit 3757b94 (ACPI / hotplug: Fix concurrency issues and > memory leaks) acpi_bus_scan() and acpi_bus_trim() must always be > called under acpi_scan_lock, but currently the following scenario > viola

[PATCH] ACPI / dock: Take ACPI scan lock in write_undock()

2013-06-15 Thread Rafael J. Wysocki
From: Rafael J. Wysocki Since commit 3757b94 (ACPI / hotplug: Fix concurrency issues and memory leaks) acpi_bus_scan() and acpi_bus_trim() must always be called under acpi_scan_lock, but currently the following scenario violating that requirement is possible: write_undock() handle_eject_reque