Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1762836ybi; Thu, 20 Jun 2019 03:23:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqwrWaILllP6NpPlQAMasq6xwld/rzohi2MxW5uSopjlUadPoL2BdYt3GSDvm4euy1SnC19p X-Received: by 2002:a65:4347:: with SMTP id k7mr12422886pgq.253.1561026226215; Thu, 20 Jun 2019 03:23:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561026226; cv=none; d=google.com; s=arc-20160816; b=fIh0kClzsqazO++BfqClNO87kkDFbAcoARkkTv+jKaYnqsOKN0K9PWytdDQlu9TAZw ArntSXzi0Xk01bw5ST5XP0j5BG7TCteNmjlWTB5Ik+oRI8K36fGJn4ME1yADJTs3sUuw EWT+9MOLh8FFWTY6QyWBrUgNP7jDBxBXt7GxwWAU/kkV/bMyTmN8fYDrOdQgrTdNBGaj jmC7w43Ce2qkbOxNpIS+OS2RaRjcfBYbHG7Gu6qQ7ZrcX9jwbEBnjzZAPZsTfbjZHBOa 2q0enf6fLpdplgOtGgxVCzfu1T9Ah6rBGS4eGAt1gnUiBt6qBNp8T8rwnawQIdcrW3Wx ykzQ== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=yFZr/HJphwpvgp8VkhQuBd7xHUUVxP6sYc7SNxe+aB0=; b=lAiYPU2KG4zZH9d62feJOZXSfwIiRK1skoZtrL1EkSuU+4+gnhPFqvrQdji6bRgJcH 04s9Bg4Uci4bc7UQwFzQRDnGxNZreu4Pux52RkZWrr9PVzT9PtReDaE3naD4DpL9NkHa FFH1KRdogF0nknisRJuyBma+vasAHkxWRLSew9jIQt4JUwE6jUxac7K8KNsNVHNjQ22Q DfSryD++cSmsepzifUDJkEQqJnBvFS5MnmaczvVXpIZJOkxQk3aGSB29TIhFcJ7+A6hJ pdRNEzU7Iiobd13Qc0bMLrTJo11h/dorGkTSztWsGuog3651hwN86Uemu/rCyv9IgV54 uk4Q== 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 v97si3764709pjb.23.2019.06.20.03.23.29; Thu, 20 Jun 2019 03:23:46 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726394AbfFTKXT (ORCPT + 99 others); Thu, 20 Jun 2019 06:23:19 -0400 Received: from www262.sakura.ne.jp ([202.181.97.72]:65081 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726081AbfFTKXT (ORCPT ); Thu, 20 Jun 2019 06:23:19 -0400 Received: from fsav108.sakura.ne.jp (fsav108.sakura.ne.jp [27.133.134.235]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id x5KANBen075520; Thu, 20 Jun 2019 19:23:11 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav108.sakura.ne.jp (F-Secure/fsigk_smtp/530/fsav108.sakura.ne.jp); Thu, 20 Jun 2019 19:23:11 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/530/fsav108.sakura.ne.jp) Received: from [192.168.1.8] (softbank126012062002.bbtec.net [126.12.62.2]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id x5KANBwb075517 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NO); Thu, 20 Jun 2019 19:23:11 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: [PATCH] hung_task: recover hung task warnings in next check interval To: Yafang Shao Cc: Andrew Morton , Dmitry Vyukov , LKML References: <1561010100-14080-1-git-send-email-laoar.shao@gmail.com> From: Tetsuo Handa Message-ID: Date: Thu, 20 Jun 2019 19:23:11 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/06/20 19:10, Yafang Shao wrote: >>> With this patch, hung task warnings will be reset with >>> sys_hung_task_warnings setting in evenry check interval. >> >> Since it is uncommon that the messages are printed for more than 10 >> times for one check_hung_uninterruptible_tasks() call, this patch is >> effectively changing to always print the messages (in other words, >> setting -1). > > If sys_hung_task_warnings can't be recovered, does it make sense to exist? > In which case do we need this setting ? Someone might want to print the messages up to only a few times because he/she does not like the ever-repeating messages. But automatically resetting will forbid his/her wish to print the messages for up to only a few times. > > Btw, why the default value of this setting is 10, instead of -1 ? I don't know. I guess just by historical reason, for this variable has been existed before support of -1 is added.