Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754259AbaDNKeV (ORCPT ); Mon, 14 Apr 2014 06:34:21 -0400 Received: from mail-ee0-f52.google.com ([74.125.83.52]:40461 "EHLO mail-ee0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750872AbaDNKeT (ORCPT ); Mon, 14 Apr 2014 06:34:19 -0400 Date: Mon, 14 Apr 2014 12:34:13 +0200 From: Ingo Molnar To: Igor Mammedov Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, bp@suse.de, paul.gortmaker@windriver.com, JBeulich@suse.com, prarit@redhat.com, drjones@redhat.com, toshi.kani@hp.com, riel@redhat.com, gong.chen@linux.intel.com, andi@firstfloor.org, lenb@kernel.org, rjw@rjwysocki.net, linux-acpi@vger.kernel.org Subject: Re: [PATCH v3 3/5] x86: fix list corruption on CPU hotplug Message-ID: <20140414103413.GB2846@gmail.com> References: <1397150061-29735-1-git-send-email-imammedo@redhat.com> <1397150061-29735-4-git-send-email-imammedo@redhat.com> <20140414091954.GB19771@gmail.com> <20140414115600.0d5dbbb5@thinkpad> <20140414100457.GD731@gmail.com> <20140414122333.0908c2a2@thinkpad> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140414122333.0908c2a2@thinkpad> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Igor Mammedov wrote: > On Mon, 14 Apr 2014 12:04:57 +0200 > Ingo Molnar wrote: > > > > > * Igor Mammedov wrote: > > > > > On Mon, 14 Apr 2014 11:19:54 +0200 > > > Ingo Molnar wrote: > > > > > > > > > > > * Igor Mammedov 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? > > Sure, I'll retest reordered series. Please don't jus test a reodered series, but a 'fixes only' series, which does not include patch #1. We will apply that patch too, to improve the bootup of virtualized environments, but we first want to know whether the 'baseline' is OK and fixed 100%. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/