diff options
authorRafael J. Wysocki <>2015-05-07 21:19:39 +0200
committerGreg Kroah-Hartman <>2015-06-06 08:19:39 -0700
commit35bcda8ac0aa75be0b7a0c72f43f80cc654679a1 (patch)
parent7063d2879259f1fa3f4f64aa18e0ae5c8a397226 (diff)
ACPI / init: Fix the ordering of acpi_reserve_resources()
commit b9a5e5e18fbf223502c0b2264c15024e393da928 upstream. Since acpi_reserve_resources() is defined as a device_initcall(), there's no guarantee that it will be executed in the right order with respect to the rest of the ACPI initialization code. On some systems this leads to breakage if, for example, the address range that should be reserved for the ACPI fixed registers is given to the PCI host bridge instead if the race is won by the wrong code path. Fix this by turning acpi_reserve_resources() into a void function and calling it directly from within the ACPI initialization sequence. Reported-and-tested-by: George McCollister <> Link: Signed-off-by: Rafael J. Wysocki <> Signed-off-by: Greg Kroah-Hartman <>
1 files changed, 2 insertions, 4 deletions
diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
index fc1aa7909690..726c969b8a81 100644
--- a/drivers/acpi/osl.c
+++ b/drivers/acpi/osl.c
@@ -172,7 +172,7 @@ static void __init acpi_request_region (struct acpi_generic_address *gas,
request_mem_region(addr, length, desc);
-static int __init acpi_reserve_resources(void)
+static void __init acpi_reserve_resources(void)
acpi_request_region(&acpi_gbl_FADT.xpm1a_event_block, acpi_gbl_FADT.pm1_event_length,
@@ -201,10 +201,7 @@ static int __init acpi_reserve_resources(void)
if (!(acpi_gbl_FADT.gpe1_block_length & 0x1))
acpi_gbl_FADT.gpe1_block_length, "ACPI GPE1_BLK");
- return 0;
void acpi_os_printf(const char *fmt, ...)
@@ -1792,6 +1789,7 @@ acpi_status __init acpi_os_initialize(void)
acpi_status __init acpi_os_initialize1(void)
+ acpi_reserve_resources();
kacpid_wq = alloc_workqueue("kacpid", 0, 1);
kacpi_notify_wq = alloc_workqueue("kacpi_notify", 0, 1);
kacpi_hotplug_wq = alloc_ordered_workqueue("kacpi_hotplug", 0);