On Friday, April 03, 2015 09:07:47 AM Bob Paauwe wrote: > While trying to make use of dynamic tables as a way to provide driver > initialization properties, I've encountered a couple of issues with the > way dynamic tables are being handled. > > The first patch appears to be a bug. There is a mutex release without > a corresponding aquire. This extra release causes a mutex error message > when a table is re-loaded after being unloaded. > > The second patch actually unloads a table when table unload is called. > When a table is being dynamically loaded by a driver module and that > driver module is unloaded, the memory for the table would typically be > freed resulting in a table that is marked as unloaded but still pointing > to that freed memory. If the driver module is then re-loaded, the > ACPI table reload function will attempt to access that freed memory when > it does a table compare and results in a oops. > > These patches solve the problems I've encountered but may not be the > proper way to solve. > > Bob Paauwe (2): > Remove extra release mutex call. > Acutally unload a table. > > drivers/acpi/acpica/tbinstal.c | 1 - > drivers/acpi/acpica/tbxfload.c | 1 + > 2 files changed, 1 insertion(+), 1 deletion(-) This is ACPICA material. Please *at* *least* CC it to the ACPICA maintainers as per MAINTAINERS, but it really should be sent to the ACPICA list (and you can CC linux-acpi if that is useful too). -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
