Re: mm: deadlock between get_online_cpus/pcpu_alloc
From: Christoph Lameter
Date: Thu Feb 09 2017 - 10:48:53 EST
On Thu, 9 Feb 2017, Thomas Gleixner wrote:
> > The stop_machine would need to ensure that all cpus cease processing
> > before proceeding.
> Ok. I try again:
> CPU 0 CPU 1
> ==> cpu = 1
> Stops processing on all CPUs by preempting the current execution and
> forcing them into a high priority busy loop with interrupts disabled.
Exactly that means we are outside of the sections marked with
> It does exactly what you describe. It stops processing on all other cpus
> until release, but that does not invalidate any data on those cpus.
Why would it need to invalidate any data? The change of the cpu masks
would need to be done when the machine is stopped. This sounds exactly
like what we need and much of it is already there.
Lets get rid of get_online_cpus() etc.