From: Aaron Lu <aaron.lu@intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Leb Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>
Subject: Re: [PATCH v2] ACPI: Fix resource_lock dead lock in acpi_power_on_device
Date: Fri, 14 Sep 2012 09:15:02 +0800 [thread overview]
Message-ID: <50528516.2020002@intel.com> (raw)
In-Reply-To: <201209140026.35993.rjw@sisk.pl>
On 09/14/2012 06:26 AM, Rafael J. Wysocki wrote:
> On Wednesday, September 12, 2012, Aaron Lu wrote:
>> Commit 0090def("ACPI: Add interface to register/unregister device
>> to/from power resources") used resource_lock to protect the devices list
>> that relies on power resource. It caused a mutex dead lock, as below
>>
>> acpi_power_on ---> lock resource_lock
>> __acpi_power_on
>> acpi_power_on_device
>> acpi_power_get_inferred_state
>> acpi_power_get_list_state ---> lock resource_lock
>>
>> This patch adds a new mutex "devices_lock" to protect the devices list
>> and calls acpi_power_on_device in acpi_power_on, instead of
>> __acpi_power_on, after the resource_lock is released.
>>
>> Signed-off-by: Lin Ming <ming.m.lin@intel.com>
>> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
>
> Good catch, thanks.
>
> I hope Len won't mind if I take it for v3.6.
>
Yes, that would be good.
And the commit enters v3.4, so a stable tag may need be added.
>> ---
>> v2:
>> If power resource is already on, no need to check if device needs
>> to be resumed.
>> v1:
>> By Lin Ming.
>>
>> drivers/acpi/power.c | 36 ++++++++++++++++++++++++------------
>> 1 file changed, 24 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/acpi/power.c b/drivers/acpi/power.c
>> index 215ecd0..3582a26 100644
>> --- a/drivers/acpi/power.c
>> +++ b/drivers/acpi/power.c
>> @@ -105,6 +105,7 @@ struct acpi_power_resource {
>>
>> /* List of devices relying on this power resource */
>> struct acpi_power_resource_device *devices;
>> + struct mutex devices_lock;
>> };
>>
>> static struct list_head acpi_power_resource_list;
>> @@ -223,7 +224,6 @@ static void acpi_power_on_device(struct acpi_power_managed_device *device)
>>
>> static int __acpi_power_on(struct acpi_power_resource *resource)
>> {
>> - struct acpi_power_resource_device *device_list = resource->devices;
>> acpi_status status = AE_OK;
>>
>> status = acpi_evaluate_object(resource->device->handle, "_ON", NULL, NULL);
>> @@ -236,19 +236,14 @@ static int __acpi_power_on(struct acpi_power_resource *resource)
>> ACPI_DEBUG_PRINT((ACPI_DB_INFO, "Power resource [%s] turned on\n",
>> resource->name));
>>
>> - while (device_list) {
>> - acpi_power_on_device(device_list->device);
>> -
>> - device_list = device_list->next;
>> - }
>> -
>> return 0;
>> }
>>
>> static int acpi_power_on(acpi_handle handle)
>> {
>> - int result = 0;
>> + int result = 0, resume_device = 0;
>
> I'll change the data type of resume_device to bool when applying the patch.
>
Sure, thanks.
-Aaron
next prev parent reply other threads:[~2012-09-14 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 9:07 [PATCH v2] ACPI: Fix resource_lock dead lock in acpi_power_on_device Aaron Lu
2012-09-13 22:26 ` Rafael J. Wysocki
2012-09-14 1:15 ` Aaron Lu [this message]
2012-09-14 1:21 ` Aaron Lu
2012-09-14 19:02 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50528516.2020002@intel.com \
--to=aaron.lu@intel.com \
--cc=aaron.lwe@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).