Re: [PATCH Resend] cpufreq: Set cpufreq_cpu_data to NULL before putting kobject

From: ethan zhao
Date: Mon Mar 09 2015 - 00:14:51 EST



On 2015/3/9 12:06, Viresh Kumar wrote:
On 9 March 2015 at 07:04, Ethan Zhao <ethan.kernel@xxxxxxxxx> wrote:
Viresh,
Got that box and did some debug, found the policy->kobj is not initialized.
So the race happened between cpufreq_cpu_get() and
__cpufreq_add_dev(), and verified 'this' race could be fixed by commit

6d4e81e cpufreq: Ref the policy object sooner

I have reboot the box with crond for more than 12 hours, no warning found.
Oh, great. Thanks for your work Ethan. You want this to be pushed for 3.18
stable kernel, right? I will see what I can do.
Of course we are happy to see it in 3.18 branch.

Thanks,
Ethan


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/