From mboxrd@z Thu Jan 1 00:00:00 1970 From: Santosh Shilimkar Subject: Re: console_cpu_notify can cause scheduling BUG during CPU hotplug Date: Tue, 26 Apr 2011 11:28:04 +0530 Message-ID: <4DB65EEC.7060604@ti.com> References: <4DB604C7.8090305@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Kevin Cernekee Cc: David.Woodhouse@intel.com, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, lethal@linux-sh.org, Michael Bohan , tj@kernel.org, simon.kagstrom@netinsight.net, mingo@elte.hu, akpm@linux-foundation.org, linux-arm-kernel@lists.infradead.org List-Id: linux-arm-msm@vger.kernel.org On 4/26/2011 5:48 AM, Kevin Cernekee wrote: > On Mon, Apr 25, 2011 at 4:33 PM, Michael Bohan wrote: >> I was curious if this scenario was accounted for in the design of the >> console CPU notifier. One workaround for this problem is to remove CPU_DEAD >> from the possible actions in console_cpu_notify(). In fact, v1-v4 of the >> patch above did not have CPU_DEAD, CPU_DYING or CPU_DOWN_FAILED in the list >> of actions. I wasn't able to track down why the other cases were added in >> the final patch. > > Here is the background information on the CPU_{DEAD,DYING,DOWN_FAILED} cases: > > http://lkml.org/lkml/2010/6/29/65 That's right. May be the change log for commit '034260d67' would have been bit more descriptive about the CPU hot-plug events. Regards Santosh