subject:"\[PATCH 2\/2\] ACPICA\: Namespace\: Fix lock order issue for namespace\/interpreter"

Re: [PATCH 2/2] ACPICA: Namespace: Fix lock order issue for namespace/interpreter

2016-07-05 Thread Rafael J. Wysocki

On Tue, Jul 5, 2016 at 7:53 AM, Lv Zheng wrote: > There is a lock order issue in acpi_load_tables(). The namespace lock is held > before holding the interpreter lock. > With ACPI_MUTEX_DEBUG enabled in kernel, we can reproduce this during boot: > [0.885699] ACPI Error: Invalid acquire order:

[PATCH 2/2] ACPICA: Namespace: Fix lock order issue for namespace/interpreter

2016-07-04 Thread Lv Zheng

There is a lock order issue in acpi_load_tables(). The namespace lock is held before holding the interpreter lock. With ACPI_MUTEX_DEBUG enabled in kernel, we can reproduce this during boot: [0.885699] ACPI Error: Invalid acquire order: Thread 405884224 owns [ACPI_MTX_Namespace], wants [ACPI