mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [2.6.33-rc5] Weird deadlock when shutting down
Date: Sun, 21 Feb 2010 17:51:14 +0800	[thread overview]
Message-ID: <2375c9f91002210151i6fe3f769k72a8a6a3485d8cf5@mail.gmail.com> (raw)
In-Reply-To: <1266674268.18465.6.camel@jlt3.sipsolutions.net>

[-- Attachment #1: Type: text/plain, Size: 501 bytes --]

On Sat, Feb 20, 2010 at 9:57 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Sat, 2010-02-20 at 21:44 +0800, Américo Wang wrote:
>
>> That message is displayed before shutting down the devices.
>>
>> To verify, you can add some printk() in the end of
>> __cpufreq_remove_dev(), or enable CONFIG_CPU_FREQ_DEBUG.
>
> That is already enabled.
>

Ok, I got it.

Could you test the patch below? Thanks!

----------------->

Signed-off-by: WANG Cong <xiyou.wangcong@gmail.com>

[-- Attachment #2: drivers-cpufreq-fix-deadlock.diff --]
[-- Type: text/plain, Size: 2078 bytes --]

diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 67bc2ec..e196084 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -1113,6 +1113,8 @@ static int __cpufreq_remove_dev(struct sys_device *sys_dev)
 	unsigned int cpu = sys_dev->id;
 	unsigned long flags;
 	struct cpufreq_policy *data;
+	struct kobject *kobj;
+	struct completion *cmp;
 #ifdef CONFIG_SMP
 	struct sys_device *cpu_sys_dev;
 	unsigned int j;
@@ -1141,10 +1143,11 @@ static int __cpufreq_remove_dev(struct sys_device *sys_dev)
 		dprintk("removing link\n");
 		cpumask_clear_cpu(cpu, data->cpus);
 		spin_unlock_irqrestore(&cpufreq_driver_lock, flags);
-		sysfs_remove_link(&sys_dev->kobj, "cpufreq");
+		kobj = &sys_dev->kobj;
 		cpufreq_cpu_put(data);
 		cpufreq_debug_enable_ratelimit();
 		unlock_policy_rwsem_write(cpu);
+		sysfs_remove_link(kobj, "cpufreq");
 		return 0;
 	}
 #endif
@@ -1181,7 +1184,10 @@ static int __cpufreq_remove_dev(struct sys_device *sys_dev)
 				data->governor->name, CPUFREQ_NAME_LEN);
 #endif
 			cpu_sys_dev = get_cpu_sysdev(j);
-			sysfs_remove_link(&cpu_sys_dev->kobj, "cpufreq");
+			kobj = &cpu_sys_dev->kobj;
+			unlock_policy_rwsem_write(cpu);
+			sysfs_remove_link(kobj, "cpufreq");
+			lock_policy_rwsem_write(cpu);
 			cpufreq_cpu_put(data);
 		}
 	}
@@ -1192,19 +1198,22 @@ static int __cpufreq_remove_dev(struct sys_device *sys_dev)
 	if (cpufreq_driver->target)
 		__cpufreq_governor(data, CPUFREQ_GOV_STOP);
 
-	kobject_put(&data->kobj);
+	kobj = &data->kobj;
+	cmp = &data->kobj_unregister;
+	unlock_policy_rwsem_write(cpu);
+	kobject_put(kobj);
 
 	/* we need to make sure that the underlying kobj is actually
 	 * not referenced anymore by anybody before we proceed with
 	 * unloading.
 	 */
 	dprintk("waiting for dropping of refcount\n");
-	wait_for_completion(&data->kobj_unregister);
+	wait_for_completion(cmp);
 	dprintk("wait complete\n");
 
+	lock_policy_rwsem_write(cpu);
 	if (cpufreq_driver->exit)
 		cpufreq_driver->exit(data);
-
 	unlock_policy_rwsem_write(cpu);
 
 	free_cpumask_var(data->related_cpus);

  reply	other threads:[~2010-02-21  9:51 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-29  4:41 Benjamin Herrenschmidt
2010-02-18  9:36 ` Johannes Berg
2010-02-18 16:31   ` Linus Torvalds
2010-02-18 18:45     ` Johannes Berg
2010-02-20  7:13       ` Américo Wang
2010-02-20  8:56         ` Johannes Berg
2010-02-20  9:06           ` Américo Wang
2010-02-20 10:53             ` Johannes Berg
2010-02-20 11:28             ` Johannes Berg
2010-02-20 12:07               ` Johannes Berg
2010-02-20 13:44               ` Américo Wang
2010-02-20 13:57                 ` Johannes Berg
2010-02-21  9:51                   ` Américo Wang [this message]
2010-02-21 10:17                     ` Johannes Berg
2010-02-22  8:19                       ` Américo Wang
2010-02-22  8:39                         ` Johannes Berg
2010-02-21 10:43                     ` Johannes Berg
2010-02-21 10:55                       ` Xiaotian Feng
2010-02-21 11:12                         ` Xiaotian Feng
2010-02-21 11:14                           ` Johannes Berg
2010-02-21 11:22                             ` Johannes Berg
2010-02-22  8:34                               ` Américo Wang
2010-02-22  9:04                                 ` Johannes Berg
2010-02-22  9:12                                   ` Américo Wang
2010-02-22  9:14                                     ` Johannes Berg
2010-02-22  9:21                                       ` Américo Wang
2010-02-22  8:22                           ` Américo Wang
2010-02-20  7:42       ` Dave Young
2010-02-20  8:46         ` Johannes Berg
2010-02-20  4:46     ` Américo Wang
2010-02-20  8:45       ` Johannes Berg
2010-02-20  9:30   ` Américo Wang
2010-02-20 10:52     ` Johannes Berg
2010-03-25 11:28 ` David Howells
2010-03-26  2:43   ` Américo Wang
2010-03-26 12:22   ` David Howells

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=2375c9f91002210151i6fe3f769k72a8a6a3485d8cf5@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®