login
Login
/
Register
Search
Forums
News
Blogs
Features
Site
Home
»
Mailing list archives
»
linux-kernel
»
2008
»
February
»
8
Re: [REGRESSION] kobject handling in cpufreq
view
thread
!MAILaRCHIVE_VOTE_RePLACE
Previous message: [
thread
] [
date
] [
author
]
Next message: [thread] [
date
] [
author
]
[view in full thread]
From:
Greg KH <gregkh@...>
To: Balaji Rao <balajirrao@...>
Cc: <linux-kernel@...>
Subject:
Re: [REGRESSION] kobject handling in cpufreq
Date: Friday, February 8, 2008 - 3:39 pm
On Sat, Feb 09, 2008 at 12:52:40AM +0530, Balaji Rao wrote:
quoted text
> Hi greg, > > I encountered a regression in linux-2.6.git which prevented the system from shutting down. I found that it > was 'waiting_for_completion' on kobj_unregister.The same thing happened when I tried to take CPUs offline. > > git-bisect pointed me to this commit : > > commit c10997f6575f476ff38442fa18fd4a0d80345f9d > Author: Greg Kroah-Hartman <gregkh@suse.de> > Date: Thu Dec 20 08:13:05 2007 -0800 > > Kobject: convert drivers/* from kobject_unregister() to kobject_put() > > In the file drivers/cpufreq/cpufreq.c, you have not replaced one occurrence of kobject_unregister with kobject_put. > Apparently its because of the kobject_put in the subsequent line. > > @@ -1030,8 +1030,6 @@ static int __cpufreq_remove_dev (struct sys_device * sys_dev) > > unlock_policy_rwsem_write(cpu); > > - kobject_unregister(&data->kobj); > - > kobject_put(&data->kobj); > > /* we need to make sure that the underlying kobj is actually > > Now, this can be fixed by adding another kobject_put. But having two kobject_puts in consequent lines tells us that there > should be two references to the kobject at that point. So, I believe that it is safe to remove the kobject_get > corresponding to the existing kobject_put to fix this. > > Signed-off-by: Balaji Rao <balajirrao@gmail.com>
This looks correct to me, nice catch. Acked-by: Greg Kroah-Hartman <gregkh@suse.de> thanks, greg k-h --
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Previous message: [
thread
] [
date
] [
author
]
Next message: [thread] [
date
] [
author
]
Messages in current thread:
[REGRESSION] kobject handling in cpufreq
, Balaji Rao
, (Fri Feb 8, 3:22 pm)
Re: [REGRESSION] kobject handling in cpufreq
, Greg KH
, (Fri Feb 8, 3:39 pm)
Navigation
Create content
Mailing list archives
Recent posts
Popular discussions
linux-kernel
:
Andrew Morton
-mm merge plans for 2.6.23
Benjamin Herrenschmidt
Re: [PATCH] Remove process freezer from suspend to RAM pathway
Greg KH
[GIT PATCH] driver core patches against 2.6.24
Mel Gorman
[PATCH 6/8] x86_64 - Specify amount of kernel memory at boot time
git
:
linux-netdev
:
Jarek Poplawski
[PATCH] pkt_sched: Destroy gen estimators under rtnl_lock().
David Miller
[GIT]: Networking
Gerrit Renker
[PATCH 15/37] dccp: Set per-connection CCIDs via socket options
Jarek Poplawski
Re: Soft-Lockup/Race in networking in 2.6.31-rc1+195 ( possibly?caused by netem)
openbsd-misc
:
Colocation donated by:
Who's online
There are currently
5 users
and
852 guests
online.
Online users
maheshdm
strcmp
please12
sethchen7712
samualwatson12
Syndicate