Re: 2.6.18-rc1-mm1

Arjan van de Ven
2006-07-10T08:50:26Z

> > - 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.

that is broken beyond discussing anyway... "we don't know our locking
rules so we do recursive mutexes" is ... NOT a good reason.