[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0hE48oR45zWqDjngS+W2JgARqqyNT5BV_nBoyhK05TcxQ@mail.gmail.com>
Date:   Thu, 27 Oct 2016 12:22:56 +0200
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Lv Zheng <zetalog@...il.com>
Cc:     "Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
        "Rafael J . Wysocki" <rjw@...ysocki.net>,
        Len Brown <len.brown@...el.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Lv Zheng <lv.zheng@...el.com>
Subject: Re: [PATCH v2 0/3] ACPICA: Interpreter: Fix regressions in lock order improvement
On Wed, Oct 26, 2016 at 9:39 AM, Lv Zheng <zetalog@...il.com> wrote:
> This patchset fixes regressions in ACPICA intepreter lock order
> improvement.
>
> Patches tested with customized ACPI table where _PS0/_PS3 methods are
> customized to invoke a serialized control method which creates named
> objects. When pm_async=yes, AE_ALREADY_EXISTS can be seen in suspend/resume
> process. This is an existing issue, triggered in 4.9-rc1 by ACPICA
> interpreter lock order fixes, and can be fixed by [PATCH 1] in this series.
>
> v2:
> 1. Remove non-regression-fixes.
> 2. Add "Fixes" tags.
>
> Lv Zheng (3):
>   ACPICA: Dispatcher: Fix order issue of method termination
>   ACPICA: Dispatcher: Fix an unbalanced lock exit path in
>     acpi_ds_auto_serialize_method()
>   ACPICA: Dispatcher: Tune interpreter lock around
>     acpi_ev_initialize_region()
Thanks!
I'm queuing up this series for the next ACPI pull request.
Thanks,
Rafael
Powered by blists - more mailing lists
 
