On Thursday, August 20, 2015 11:20:28 PM Yinghai Lu wrote: > We check the realloc list, as list must be empty after allocation. > > Add missing one acpiphp driver. > > Signed-off-by: Yinghai Lu <yinghai@xxxxxxxxxx> > Cc: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx> > Cc: Len Brown <lenb@xxxxxxxxxx> > Cc: linux-acpi@xxxxxxxxxxxxxxx > --- > drivers/pci/hotplug/acpiphp_glue.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/pci/hotplug/acpiphp_glue.c b/drivers/pci/hotplug/acpiphp_glue.c > index ff53856..1c7c1d7 100644 > --- a/drivers/pci/hotplug/acpiphp_glue.c > +++ b/drivers/pci/hotplug/acpiphp_glue.c > @@ -507,6 +507,7 @@ static void enable_slot(struct acpiphp_slot *slot) > } > } > __pci_bus_assign_resources(bus, &add_list, NULL); > + BUG_ON(!list_empty(&add_list)); Is crashing the kernel the best we can do here? What about bailing out with a WARN_ON() instead? Surely, the kernel can work without the new device? > > acpiphp_sanitize_bus(bus); > pcie_bus_configure_settings(bus); > -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
