Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp1744133ybi; Thu, 20 Jun 2019 03:04:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqy/D+qSYVNGRnZ23E51Lctn6/nBkE60d2z45gLfT4ddgw01vimzra7zH88GU+PW1N8lTdea X-Received: by 2002:a63:1316:: with SMTP id i22mr12630850pgl.274.1561025061435; Thu, 20 Jun 2019 03:04:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561025061; cv=none; d=google.com; s=arc-20160816; b=OPMMKvxCh3x0aMM3TnraZujy5CdhRtWFzQBjS3yRx4LujRH10aWylZDR3OpWJMCnzO MptXH3FP5wd2C4DD6unOlkZX5JuMqYUM5Auu1Q3V/YlcAAThXn9v4v/H9zzm2tJg4SuK SWea7OATTAEn1LqRZx73xtEVQTVah4HUbyj9ykPexGp5KGnsSzm1hmvaUEzL8vnXt5QY 13QDD2iRlMOxRC0hrZS5wdESzmYLtxFsnF2xArPfCKxxwsgM99rlDNe0wAA7XXR8pPD6 dVpTnmlgt5Wu2UD29IFvUEGpVOMlLOjJnc3xJWGHl5hwVHG4nB048a2t8WZojq+VGDxQ VfOw== 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=0F95vUbH59+ovM1mcSrF44DksCqLjftELkRBVEypOTQ=; b=z4oIPLoSChbvm0XvpGVnkKBZdEwufB/jQ5dTx/jGWqPtagJUh4db8LC+dPJr12QD5y xbR+GoE0AAjT5aFNtH3XUt0+QvhkVkcChRw85aCMbtjC0XJS4eD1aHKywVJk6Ci1zAUy 0xDkduLapQNpzJexvOer3ok492j+e3DR1+/hfoVYvZvRyz06kK7NwaaibEJRFTI8MpHy j+xL+kZ5ZOEegczUJUGF6rf1DELzVbgjygd1phFomBBxMUx7h+d5IDUIr7+DDbp4syN0 ZPVl36mVyaJZWGspSPrp+ZIdQkxDbRqP3Dfdmpz+RFLlrMJKmR5AxrTjI/aP9B253m8o l4GA== 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 21si1742932pfa.144.2019.06.20.03.04.04; Thu, 20 Jun 2019 03:04:21 -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 S1731504AbfFTKDL (ORCPT + 99 others); Thu, 20 Jun 2019 06:03:11 -0400 Received: from www262.sakura.ne.jp ([202.181.97.72]:64167 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726268AbfFTKDL (ORCPT ); Thu, 20 Jun 2019 06:03:11 -0400 Received: from fsav405.sakura.ne.jp (fsav405.sakura.ne.jp [133.242.250.104]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id x5KA33mw058292; Thu, 20 Jun 2019 19:03:03 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav405.sakura.ne.jp (F-Secure/fsigk_smtp/530/fsav405.sakura.ne.jp); Thu, 20 Jun 2019 19:03:03 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/530/fsav405.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 x5KA2w9u058271 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NO); Thu, 20 Jun 2019 19:03:03 +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 , akpm@linux-foundation.org, dvyukov@google.com Cc: linux-kernel@vger.kernel.org References: <1561010100-14080-1-git-send-email-laoar.shao@gmail.com> From: Tetsuo Handa Message-ID: Date: Thu, 20 Jun 2019 19:02:57 +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: <1561010100-14080-1-git-send-email-laoar.shao@gmail.com> 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 14:55, Yafang Shao wrote: > When sys_hung_task_warnings reaches 0, the hang task messages will not > be reported any more. It is a common mistake that sys_hung_task_warnings is already 0 when a real problem which should be reported occurred. > > If the user want to get more hung task messages, he must reset > kernel.hung_task_warnings to a postive integer or -1 with sysctl. People are setting sys_hung_task_warnings to -1 in order to make sure that the messages are printed. > This is not a good way for the user. But I don't think we should reset automatically. > We'd better reset hung task warnings in the kernel, and then the user > don't need to pay attention to this value. I suggest changing the default value of sys_hung_task_warnings to -1. > > 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).