Re: 2.6.18-rc1-mm1

Nick Piggin
2006-07-09T14:38:39Z

Nick Piggin wrote:
> Andrew Morton wrote:

>>
>> - If a piece of kernel code is dealing with per-cpu data and cannot run
>> atomically then it should have its own cpu hotplug handlers anyway. It
>> is up to that code (ie: cpufreq) to provide its own locking against its
>> own CPU hotplug callback.
>
>
> This still does not solve this cpufreq problem where it is trying to
> take the same lock twice down the same call path. Whether it is the
> lock_cpu_hotplug mutex or another one, the code must be just busted.
>

Err...

s/twice down the same call path/inverted with another lock

--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com