From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751489AbdJEQRT (ORCPT ); Thu, 5 Oct 2017 12:17:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46278 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751144AbdJEQRR (ORCPT ); Thu, 5 Oct 2017 12:17:17 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 2C30D7AE97 Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=dzickus@redhat.com Date: Thu, 5 Oct 2017 12:17:14 -0400 From: Don Zickus To: Thomas Gleixner Cc: Michael Ellerman , LKML , Ingo Molnar , Peter Zijlstra , Borislav Petkov , Andrew Morton , Sebastian Siewior , Nicholas Piggin , Chris Metcalf , Ulrich Obergfell , Benjamin Herrenschmidt , linuxppc-dev@lists.ozlabs.org Subject: Re: [patch V2 22/29] lockup_detector: Make watchdog_nmi_reconfigure() two stage Message-ID: <20171005161714.nlmmqhrqkqzc3gst@redhat.com> References: <20170912193654.321505854@linutronix.de> <20170912194147.862865570@linutronix.de> <87d165dqew.fsf@concordia.ellerman.id.au> <87o9pocvjq.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170914 (1.9.0) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Thu, 05 Oct 2017 16:17:17 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Archived-At: List-Archive: List-Post: On Tue, Oct 03, 2017 at 07:27:01PM +0000, Thomas Gleixner wrote: > On Tue, 3 Oct 2017, Thomas Gleixner wrote: > > On Tue, 3 Oct 2017, Thomas Gleixner wrote: > > > On Tue, 3 Oct 2017, Michael Ellerman wrote: > > > > Hmm, I tried that patch, it makes the warning go away. But then I > > > > triggered a deliberate hard lockup and got nothing. > > > > > > > > Then I went back to the existing code (in linux-next), and I still get > > > > no warning from a deliberate hard lockup. > > > > > > > > So seems there may be some more gremlins. Will test more in the morning. > > > > > > Hrm. That's weird. I'll have a look and send a proper patch series on top > > > of next. > > > > The major difference is that the reworked code utilizes > > watchdog_nmi_reconfigure() for both init and the sysctl updates, but I > > can't for my life figure out why that doesn't work. > > I collected the changes which Linus requested along with the nmi_probe() > one and pushed them into: > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.core/urgent > > That's based on 4.13 final so it neither contains 4.14 nor -next material. Tested your changes on 4.14-rc3 and it passes my tests. Thanks! Tested-and-Reviewed-by: Don Zickus