Re: [PATCH] cpufreq: fix another race between PPC notification and vcpu_hotplug()

2015-01-29 Thread Viresh Kumar
On 30 January 2015 at 07:14, ethan zhao wrote: > Please take a look at the code I composed, I thought of it whole night. Santosh has already tested my patch and it worked for him. And that is the right solution I believe. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel"

Re: [PATCH] cpufreq: fix another race between PPC notification and vcpu_hotplug()

2015-01-29 Thread ethan zhao
Viresh, On 2015/1/29 16:38, Viresh Kumar wrote: Looks like you just save my time here, Santosh has also reported a similar race in a personal mail.. As you know, Santosh is in the same cage as me. On 29 January 2015 at 12:12, Ethan Zhao wrote: There is race observed between PPC changed not

Re: [PATCH] cpufreq: fix another race between PPC notification and vcpu_hotplug()

2015-01-29 Thread santosh shilimkar
On 1/29/2015 12:38 AM, Viresh Kumar wrote: Looks like you just save my time here, Santosh has also reported a similar race in a personal mail.. On 29 January 2015 at 12:12, Ethan Zhao wrote: There is race observed between PPC changed notification handler worker thread and vcpu_hotplug() called

Re: [PATCH] cpufreq: fix another race between PPC notification and vcpu_hotplug()

2015-01-29 Thread Viresh Kumar
Looks like you just save my time here, Santosh has also reported a similar race in a personal mail.. On 29 January 2015 at 12:12, Ethan Zhao wrote: > There is race observed between PPC changed notification handler worker thread > and vcpu_hotplug() called within xenbus_thread() context. > It is s

[PATCH] cpufreq: fix another race between PPC notification and vcpu_hotplug()

2015-01-28 Thread Ethan Zhao
There is race observed between PPC changed notification handler worker thread and vcpu_hotplug() called within xenbus_thread() context. It is shown as following WARNING: [ cut here ] WARNING: CPU: 0 PID: 4 at include/linux/kref.h:47 kobject_get+0x41/0x50() Modules linke