Re: [PATCH v3 0/7] ACPI / hotplug / PCI: Consolidation of ACPIPHP with ACPI core device hotplug

From: Rafael J. Wysocki
Date: Mon Feb 03 2014 - 16:36:49 EST

On Monday, February 03, 2014 12:45:11 PM Mika Westerberg wrote:
> On Sun, Feb 02, 2014 at 06:11:19PM +0100, Rafael J. Wysocki wrote:
> > As stated in the message at ,
> > patch [1/6] was actaully wrong and the whole patchset had to be reworked for that
> > reason. What follows is an entirely new version:
> >
> > [1/7] Add a new function to ACPICA allowing a callback to be executed under the
> > namespace mutex after calling acpi_ns_get_attached_data().
> >
> > [2/7] Use the new ACPICA's function to fix a couple of potential races related
> > to ACPI notifies.
> >
> > [3/7] Same as [2/6] above.
> > [4/7] Same as [3/6] above, rebased.
> > [5/7] Same as [4/6] above.
> > [6/7] Same as [5/6] above.
> > [7/7] Dispatch ACPI hotplug notifications for "core" devices and PCI from
> > acpi_bus_notify(). This actually is different from [6/6] above, although
> > it serves the same purpose.
> >
> On Intel NUC and DZ77RE-75K,
> Tested-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>

Thanks a lot for testing!

In the meantime, though, I found two more race conditions in ACPIPHP related to
races with sysfs-triggered device remove. I have patches to fix them, but then
I had to rebase this series (and the ACPIPHP one this is based on) on top of
those fixes.

I'm going to resend the two patchsets as one series including the fixes
mentioned above. I tried to avoid sending out a series of 20+ patches, because
then it's almost guaranteed that no one will look at them unless they happen to
break things in testing, but I guess I have no choice but to do that at this


I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at