Received: by 10.223.176.5 with SMTP id f5csp1216922wra; Tue, 6 Feb 2018 15:02:31 -0800 (PST) X-Google-Smtp-Source: AH8x224XoMD7j6sdUfaeeJE8jXr5iy6HFWmiz1/9vG/R6aO+Zlmc1KLEivLxmFgVx2WFTJy13YsS X-Received: by 10.101.64.204 with SMTP id u12mr345046pgp.280.1517958151192; Tue, 06 Feb 2018 15:02:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517958151; cv=none; d=google.com; s=arc-20160816; b=NshC2E1Y9txxeBgfA7PERg3N3BN3xSiNOpeN/rbSOi3I0q+nFVFiaRhZbynYKNZLLm AVcVxrA0BM0ARc0RtEOvXk36YJ52RgytVAm6sq2zIGiwN3M2rjr7DkUtW76tGxm5lvt1 bIimMJ32Mcv+xnEA6nPp4yBrfYcVFWQDeLQkK4JXQZ+OdC+UFXhRpq01jOwvEG3/UXaP 6bSkiUMqz7c+uag8mLxiXZroFjHm0JPHV/LxACoWHn3/Ditd/ig+uYiLa7jDEI4PmYKy Wg5wkQGyGPBTCvwIq4EJNNaz2lsFpeHFFi06/2hom9BIO4/9sjlTRdt6K+bjIH0HrhYZ hf/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from:arc-authentication-results; bh=bp8wiX73d6jF3f7wSfM/7U8ki4ifHsRRTxDlxBO5+1U=; b=lqCOdBpSO7HLWxO0abCHfcIYHRaAjqkbNwspEL4w4ObLNS2eIfViYICEHHG0XwagrB hfUm7Je/Rr3MD1AsGDUJiRmtrfEROICQ2VEk1sn2sqqIU7v1zvX4tPPBN43CSqlFaFDY yQ5CDofW5kTgUM2UiLYr7h4GAJn0/8kcCiNLjTuQyhU2QNhxDCvD2AwUkQIcLVtYoaDu s9QrXRtCMMTKGhEfLCW70sDCjHaPd8Dhj4h7qgjU8lEVODQ+/DpfrvYsk2cxD7x5oiK0 rGvbkrpjk40oGjPhEDtxi+kQKJnDAQDzwBcpoLnfY8QXZgkVtdOPKqV1Jk/4AeCDeks0 +73Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c20si63229pfk.415.2018.02.06.15.02.15; Tue, 06 Feb 2018 15:02:31 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753999AbeBFXAs (ORCPT + 99 others); Tue, 6 Feb 2018 18:00:48 -0500 Received: from g2t1383g.austin.hpe.com ([15.233.16.89]:13050 "EHLO g2t1383g.austin.hpe.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753704AbeBFXAR (ORCPT ); Tue, 6 Feb 2018 18:00:17 -0500 Received: from g4t3426.houston.hpe.com (g4t3426.houston.hpe.com [15.241.140.75]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by g2t1383g.austin.hpe.com (Postfix) with ESMTPS id 658BA15E2; Tue, 6 Feb 2018 23:00:17 +0000 (UTC) Received: from g9t2301.houston.hpecorp.net (g9t2301.houston.hpecorp.net [16.220.97.129]) by g4t3426.houston.hpe.com (Postfix) with ESMTP id BF93D60; Tue, 6 Feb 2018 23:00:16 +0000 (UTC) Received: from anatevka.ftc.rdlabs.hpecorp.net (anatevka.americas.hpqcorp.net [10.34.81.6]) by g9t2301.houston.hpecorp.net (Postfix) with ESMTP id 5AFDB60; Tue, 6 Feb 2018 23:00:16 +0000 (UTC) From: Jerry Hoemann To: wim@linux-watchdog.org, linux@roeck-us.net Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org, rwright@hpe.com, maurice.a.saldivar@hpe.com, Jerry Hoemann Subject: [PATCH 10/10] watchdog/hpwdt: remove allow_kdump module parameter. Date: Tue, 6 Feb 2018 15:58:55 -0700 Message-Id: <20180206225855.30582-11-jerry.hoemann@hpe.com> X-Mailer: git-send-email 2.13.6 In-Reply-To: <20180206225855.30582-1-jerry.hoemann@hpe.com> References: <20180206225855.30582-1-jerry.hoemann@hpe.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The intent of this parameter is unclear and it sets up a race between the reset of the system by ASR and crashdump. The length of time between receipt of the pretimeout NMI and the ASR reset of the system is fixed by hardware. Turning the parameter off doesn't necessairly prevent a crash dump. Also, having the ASR reset occur while the system is crash dumping doesn't imply that the dump was hung given the short duration between the NMI and the reset. This parameter is not a substitute for having a architected watchdog crashdump hang detection paridigm. Signed-off-by: Jerry Hoemann --- drivers/watchdog/hpwdt.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c index 9bfb668115f8..f767ea4dba86 100644 --- a/drivers/watchdog/hpwdt.c +++ b/drivers/watchdog/hpwdt.c @@ -32,7 +32,6 @@ static unsigned int soft_margin = DEFAULT_MARGIN; /* in seconds */ static bool nowayout = WATCHDOG_NOWAYOUT; -static unsigned int allow_kdump = 1; static bool iLO5; #ifdef CONFIG_HPWDT_NMI_DECODING /* { */ static bool pretimeout = 1; @@ -149,8 +148,7 @@ static int hpwdt_pretimeout(unsigned int ulReason, struct pt_regs *regs) if (iLO5 && (ulReason == NMI_UNKNOWN) && !mynmi) return NMI_DONE; - if (allow_kdump) - hpwdt_stop(&hpwdt_dev); + hpwdt_stop(&hpwdt_dev); panic_msg[0] = hexdigit((mynmi>>4)&0xf); panic_msg[1] = hexdigit(mynmi&0xf); @@ -347,9 +345,6 @@ MODULE_PARM_DESC(nowayout, "Watchdog cannot be stopped once started (default=" __MODULE_STRING(WATCHDOG_NOWAYOUT) ")"); #ifdef CONFIG_HPWDT_NMI_DECODING /* { */ -module_param(allow_kdump, int, 0444); -MODULE_PARM_DESC(allow_kdump, "Start a kernel dump after NMI occurs"); - module_param(pretimeout, bool, 0444); MODULE_PARM_DESC(pretimeout, "Watchdog pretimeout enabled"); #endif /* } */ -- 2.13.6