[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140414100457.GD731@gmail.com>
Date: Mon, 14 Apr 2014 12:04:57 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Igor Mammedov <imammedo@...hat.com>
Cc: linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, x86@...nel.org, bp@...e.de,
paul.gortmaker@...driver.com, JBeulich@...e.com, prarit@...hat.com,
drjones@...hat.com, toshi.kani@...com, riel@...hat.com,
gong.chen@...ux.intel.com, andi@...stfloor.org, lenb@...nel.org,
rjw@...ysocki.net, linux-acpi@...r.kernel.org
Subject: Re: [PATCH v3 3/5] x86: fix list corruption on CPU hotplug
* Igor Mammedov <imammedo@...hat.com> wrote:
> On Mon, 14 Apr 2014 11:19:54 +0200
> Ingo Molnar <mingo@...nel.org> wrote:
>
> >
> > * Igor Mammedov <imammedo@...hat.com> wrote:
> >
> > > currently if AP wake up is failed, master CPU marks AP as not present
> > > in do_boot_cpu() by calling set_cpu_present(cpu, false).
> > > That leads to following list corruption on the next physical CPU
> > > hotplug:
> >
> > Shouldn't this fix precede the main change to the smp bootup logic?
> >
> > Can this bug trigger with current upstream kernels?
> That's not impossible, tests showed that with current kernel there will
> be other problems due wild AP running around.
>
> I'll reorder patch anyway.
So, could you please first make sure that with only the fixes applied
there's no problems left?
Only then should we apply the patch that adds/tweaks the timeout/etc.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists