Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752268AbbGLDKF (ORCPT ); Sat, 11 Jul 2015 23:10:05 -0400 Received: from g9t5008.houston.hp.com ([15.240.92.66]:49789 "EHLO g9t5008.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752092AbbGLDKE (ORCPT ); Sat, 11 Jul 2015 23:10:04 -0400 Message-ID: <55A1DA85.3090803@hp.com> Date: Sat, 11 Jul 2015 23:09:57 -0400 From: Waiman Long User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Masami Hiramatsu CC: Peter Zijlstra , Ingo Molnar , Ingo Molnar , linux-kernel Subject: Re: [BUG][tip/master] kernel panic while locking selftest at qspinlock_paravirt.h:137! References: <559FAD5E.3080309@hitachi.com> <20150710130028.GI19282@twins.programming.kicks-ass.net> <20150710135746.GA13461@gmail.com> <20150710142824.GK19282@twins.programming.kicks-ass.net> <55A06439.90002@hitachi.com> <55A07111.6030900@hp.com> <55A0A413.7020507@hitachi.com> In-Reply-To: <55A0A413.7020507@hitachi.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1585 Lines: 35 On 07/11/2015 01:05 AM, Masami Hiramatsu wrote: > On 2015/07/11 10:27, Waiman Long wrote: >> On 07/10/2015 08:32 PM, Masami Hiramatsu wrote: >>> On 2015/07/10 23:28, Peter Zijlstra wrote: >>>> On Fri, Jul 10, 2015 at 03:57:46PM +0200, Ingo Molnar wrote: >>>>> * Peter Zijlstra wrote: >>>>>> Do we want to make double unlock non-fatal unconditionally? >>>>> No, just don't BUG() out, don't crash the system - generate a warning? >>>> So that would be a yes.. >>>> >>>> Something like so then? Won't this generate a splat on that locking self >>>> test then? And upset people? >>> Hmm, yes, this still noisy... >>> Can't we avoid double-unlock completely? it seems that this warning can >>> happen randomly, which means pv-spinlock randomly broken, doesn't it? >> It shouldn't randomly happen. The message should be printed at the first >> instance of double-unlock. If that is not case, there may be some >> problem in the code. > Ah, OK. That comes from locking selftest. In that case, do we really > need the warning while selftest, since we know it always fails ? > >> Anyway, I have an alternative fix that should better capture the problem: > Do we need both Peter's BUG() removing patch and this? > No, you can choose either one. They are just different ways to solve the same BUG() problem. Cheers, Longman -- 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/