Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4155375ybb; Mon, 23 Mar 2020 14:47:10 -0700 (PDT) X-Google-Smtp-Source: ADFU+vsAGHqfczG3F3GcBNzd3mQsLs8+yj79d4BoYj61Xc9xfkr0j/3cozAN1qfld6UPobZK18w7 X-Received: by 2002:a05:6808:43:: with SMTP id v3mr1158681oic.59.1585000030556; Mon, 23 Mar 2020 14:47:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585000030; cv=none; d=google.com; s=arc-20160816; b=GqdZdDe99/VBYhztD9nXK1jqrY1BmpBCw5OVdG/TuKjej4YIM1y90XKPS7YyVghQka JNZi3ZNfBxzRuXkyglt8E7q7fo8ZGcpW93+50ZfY1y5X0wHJD6Qv7zAKiVINzxqd8HT0 Jw5dVem4j2hMYJy48DM8L/PmcIAlEcupXCit0pgLrh/a0G+i/Nj5bXxBo1+3gkNhNfq7 WDPz4ZTXTm9wkqGfyu6U1Fn/8VtKma6cehijvjlVYnfmykouwanpxacIe/mpvbwd96lJ 0MedxQRZYW9dCZ8ekoo0vmEYJDjA6kkYyuXzOJP/DUgl5vzk2wESpqEvYjWVczYzt5Hy K7Wg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from; bh=IyEq9cC0p84R074N8knqi4eTkTH1auwI+4lEtYST0ds=; b=J40cXyC4NpnVo0BBWOZIZ3mZ0VepSZaDph6ZoJkIPrLAQ5OLWq6eOPjMpjPA3M/+Ne VTaP/LijF6BsszGJTXivINHGhpANv0mnu4Gloc75g/tD5vSC0nclUsjneL45V06Fg72C 8Uh5Dpb8YJ0A0w5u0D6GN67PNwuas3dONWN0E+7lf/yjZEByBkggla5iIS8nvV38MaW3 lUyzUbbNxSfSthLbq9tBuZ05RZIQlgAnO2quP8okZapJurSUq3sH5nfJDnXW1FB24HiJ WM091b7XQggV3pPWSzpkiv4XeM138bEsd+yU1kdUoOU6H9M5kFWowiVfttBY/pynEIXY RTzQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l16si8740070oti.106.2020.03.23.14.46.57; Mon, 23 Mar 2020 14:47:10 -0700 (PDT) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727050AbgCWVq1 (ORCPT + 99 others); Mon, 23 Mar 2020 17:46:27 -0400 Received: from youngberry.canonical.com ([91.189.89.112]:41308 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727025AbgCWVq1 (ORCPT ); Mon, 23 Mar 2020 17:46:27 -0400 Received: from mail-qk1-f198.google.com ([209.85.222.198]) by youngberry.canonical.com with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1jGUts-0004qs-6a for linux-kernel@vger.kernel.org; Mon, 23 Mar 2020 21:46:24 +0000 Received: by mail-qk1-f198.google.com with SMTP id 64so6288178qkk.1 for ; Mon, 23 Mar 2020 14:46:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=IyEq9cC0p84R074N8knqi4eTkTH1auwI+4lEtYST0ds=; b=mjk14EQouC+koK1e9puczdX6SLyI3O0YGh8ulFQvSGnyAOv9oMPBOGmsMONi4Ux+rI Krt9sY9Nvx03KgM655j009ApzF41BSgwOchAhnQD/nwz2pFl9L1gXGaubacA2mkmPYPf 8ePWEKj0w9Ymf3ErgzspyxcNBYBpl2d6vqs5a8n1WxsqxNM9KgnHiMjJE7ecyWvrzS0A 8GkaYwZQlmfpcw9tDBSmFkGq2Enct6v7QaPsaR3al7Lr36uowwd9wA0a1zyADzIy5472 RY01mW140XUZUBsLsFR/4lI7WMv/+aMyrscCawhKyYEX8w0oK+QZAYISNIAyUZ5Ia2qm zrPA== X-Gm-Message-State: ANhLgQ0BcjSCOP9ovcKPBDkKuH/SwVuBw/jNOi57Qp8aatX7M5JH80Ek BW38a8vpUpQWX3kJQ9+Lxh5YVnSOG1mQ2Mz+ONNw3omfenOGykKC8MN1H0FXdQfHLlR0ai9obXt R2NaixCulZrig/LcVd616UzU/x13OB0WT+qOvmP7T5w== X-Received: by 2002:a37:6244:: with SMTP id w65mr23140458qkb.350.1584999982756; Mon, 23 Mar 2020 14:46:22 -0700 (PDT) X-Received: by 2002:a37:6244:: with SMTP id w65mr23140424qkb.350.1584999982307; Mon, 23 Mar 2020 14:46:22 -0700 (PDT) Received: from localhost (189-47-87-73.dsl.telesp.net.br. [189.47.87.73]) by smtp.gmail.com with ESMTPSA id 5sm3398651qka.16.2020.03.23.14.46.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2020 14:46:21 -0700 (PDT) From: "Guilherme G. Piccoli" To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Cc: linux-doc@vger.kernel.org, mcgrof@kernel.org, keescook@chromium.org, yzaikin@google.com, tglx@linutronix.de, penguin-kernel@I-love.SAKURA.ne.jp, akpm@linux-foundation.org, cocci@systeme.lip6.fr, linux-api@vger.kernel.org, gpiccoli@canonical.com, kernel@gpiccoli.net Subject: [PATCH V2] kernel/hung_task.c: Introduce sysctl to print all traces when a hung task is detected Date: Mon, 23 Mar 2020 18:46:18 -0300 Message-Id: <20200323214618.28429-1-gpiccoli@canonical.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit 401c636a0eeb ("kernel/hung_task.c: show all hung tasks before panic") introduced a change in that we started to show all CPUs backtraces when a hung task is detected _and_ the sysctl/kernel parameter "hung_task_panic" is set. The idea is good, because usually when observing deadlocks (that may lead to hung tasks), the culprit is another task holding a lock and not necessarily the task detected as hung. The problem with this approach is that dumping backtraces is a slightly expensive task, specially printing that on console (and specially in many CPU machines, as servers commonly found nowadays). So, users that plan to collect a kdump to investigate the hung tasks and narrow down the deadlock definitely don't need the CPUs backtrace on dmesg/console, which will delay the panic and pollute the log (crash tool would easily grab all CPUs traces with 'bt -a' command). Also, there's the reciprocal scenario: some users may be interested in seeing the CPUs backtraces but not have the system panic when a hung task is detected. The current approach hence is almost as embedding a policy in the kernel, by forcing the CPUs backtraces' dump (only) on hung_task_panic. This patch decouples the panic event on hung task from the CPUs backtraces dump, by creating (and documenting) a new sysctl/kernel parameter called "hung_task_all_cpu_backtrace", analog to the approach taken on soft/hard lockups, that have both a panic and an "all_cpu_backtrace" sysctl to allow individual control. The new mechanism for dumping the CPUs backtraces on hung task detection respects "hung_task_warnings" by not dumping the traces in case there's no warnings left. Cc: Tetsuo Handa Signed-off-by: Guilherme G. Piccoli --- V2: Followed suggestions from Kees and Tetsuo (and other grammar improvements). Also, followed Tetsuo suggestion to itereate kernel testing community - but I don't really know a ML for that, so I've CCed Coccinelle community and kernel-api ML. Also, Tetsuo suggested that this option could be default to 1 - I'm open to it, but given it is only available if hung_task panic is set as of now and the goal of this patch is give users more flexibility, I vote to keep default as 0. I can respin a V3 in case more people want to see it enabled by default. Thanks in advance for the review! Cheers, Guilherme .../admin-guide/kernel-parameters.txt | 6 ++++ Documentation/admin-guide/sysctl/kernel.rst | 15 ++++++++++ include/linux/sched/sysctl.h | 7 +++++ kernel/hung_task.c | 30 +++++++++++++++++-- kernel/sysctl.c | 11 +++++++ 5 files changed, 67 insertions(+), 2 deletions(-) diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt index c07815d230bc..7a14caac6c94 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -1453,6 +1453,12 @@ x86-64 are 2M (when the CPU supports "pse") and 1G (when the CPU supports the "pdpe1gb" cpuinfo flag). + hung_task_all_cpu_backtrace= + [KNL] Should kernel generate backtraces on all cpus + when a hung task is detected. Defaults to 0 and can + be controlled by hung_task_all_cpu_backtrace sysctl. + Format: + hung_task_panic= [KNL] Should the hung task detector generate panics. Format: diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst index def074807cee..8b4ff69d2348 100644 --- a/Documentation/admin-guide/sysctl/kernel.rst +++ b/Documentation/admin-guide/sysctl/kernel.rst @@ -40,6 +40,7 @@ show up in /proc/sys/kernel: - hotplug - hardlockup_all_cpu_backtrace - hardlockup_panic +- hung_task_all_cpu_backtrace - hung_task_panic - hung_task_check_count - hung_task_timeout_secs @@ -338,6 +339,20 @@ Path for the hotplug policy agent. Default value is "/sbin/hotplug". +hung_task_all_cpu_backtrace: +================ + +If this option is set, the kernel will send an NMI to all CPUs to dump +their backtraces when a hung task is detected. This file shows up if +CONFIG_DETECT_HUNG_TASK and CONFIG_SMP are enabled. + +0: Won't show all CPUs backtraces when a hung task is detected. +This is the default behavior. + +1: Will non-maskably interrupt all CPUs and dump their backtraces when +a hung task is detected. + + hung_task_panic: ================ diff --git a/include/linux/sched/sysctl.h b/include/linux/sched/sysctl.h index d4f6215ee03f..8cd29440ec8a 100644 --- a/include/linux/sched/sysctl.h +++ b/include/linux/sched/sysctl.h @@ -7,6 +7,13 @@ struct ctl_table; #ifdef CONFIG_DETECT_HUNG_TASK + +#ifdef CONFIG_SMP +extern unsigned int sysctl_hung_task_all_cpu_backtrace; +#else +#define sysctl_hung_task_all_cpu_backtrace 0 +#endif /* CONFIG_SMP */ + extern int sysctl_hung_task_check_count; extern unsigned int sysctl_hung_task_panic; extern unsigned long sysctl_hung_task_timeout_secs; diff --git a/kernel/hung_task.c b/kernel/hung_task.c index 14a625c16cb3..0d76f9d25820 100644 --- a/kernel/hung_task.c +++ b/kernel/hung_task.c @@ -53,9 +53,28 @@ int __read_mostly sysctl_hung_task_warnings = 10; static int __read_mostly did_panic; static bool hung_task_show_lock; static bool hung_task_call_panic; +static bool hung_task_show_all_bt; static struct task_struct *watchdog_task; +#ifdef CONFIG_SMP +/* + * Should we dump all CPUs backtraces in a hung task event? + * Defaults to 0, can be changed either via cmdline or sysctl. + */ +unsigned int __read_mostly sysctl_hung_task_all_cpu_backtrace; + +static int __init hung_task_backtrace_setup(char *str) +{ + int rc = kstrtouint(str, 0, &sysctl_hung_task_all_cpu_backtrace); + + if (rc) + return rc; + return 1; +} +__setup("hung_task_all_cpu_backtrace=", hung_task_backtrace_setup); +#endif /* CONFIG_SMP */ + /* * Should we panic (and reboot, if panic_timeout= is set) when a * hung task is detected: @@ -137,6 +156,9 @@ static void check_hung_task(struct task_struct *t, unsigned long timeout) " disables this message.\n"); sched_show_task(t); hung_task_show_lock = true; + + if (sysctl_hung_task_all_cpu_backtrace) + hung_task_show_all_bt = true; } touch_nmi_watchdog(); @@ -201,10 +223,14 @@ static void check_hung_uninterruptible_tasks(unsigned long timeout) rcu_read_unlock(); if (hung_task_show_lock) debug_show_all_locks(); - if (hung_task_call_panic) { + + if (hung_task_show_all_bt) { + hung_task_show_all_bt = false; trigger_all_cpu_backtrace(); + } + + if (hung_task_call_panic) panic("hung_task: blocked tasks"); - } } static long hung_timeout_jiffies(unsigned long last_checked, diff --git a/kernel/sysctl.c b/kernel/sysctl.c index ad5b88a53c5a..238f268de486 100644 --- a/kernel/sysctl.c +++ b/kernel/sysctl.c @@ -1098,6 +1098,17 @@ static struct ctl_table kern_table[] = { }, #endif #ifdef CONFIG_DETECT_HUNG_TASK +#ifdef CONFIG_SMP + { + .procname = "hung_task_all_cpu_backtrace", + .data = &sysctl_hung_task_all_cpu_backtrace, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = SYSCTL_ZERO, + .extra2 = SYSCTL_ONE, + }, +#endif /* CONFIG_SMP */ { .procname = "hung_task_panic", .data = &sysctl_hung_task_panic, -- 2.25.1