From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-174.mta0.migadu.com (out-174.mta0.migadu.com [91.218.175.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 02B44431E5F for ; Tue, 4 Aug 2026 04:13:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.174 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785816816; cv=none; b=OuW6NJ41iKKO6EVgtvK7VC9nSW+IdtdcsJWI9qApvyLeKGWRSfdW8urx9okHl7RCI/F5VlM2eX45SdNm1UVioHILcqr/lbV9bMdKGSgdA2mMzn2OdQTT9L7+zIQL2jjyMFolhy+pJHmV38dzW296nehpFfd6c9HowrKjgU1Pbc0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785816816; c=relaxed/simple; bh=FM4uBXU0Fe7orQha21mEGCioaWtdaQLN9aUonumnYDg=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=JyMsRXIcaCPZw5bFu7lTjWWCAr+pc8Ln8JExBr1DZZQOWIfmjAykeVgbQLGmpgSh2hagFm1RTmtZvy3syvi6mCqymwTp2zfeySOuH5UBnYzhCVEEp2uhwxMqXjG4PhqcOXrXZl16hKkSJ0sJBkhmyLEa+lJVBn9sQBFgd3mj4aQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=A9oxmLiL; arc=none smtp.client-ip=91.218.175.174 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="A9oxmLiL" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1785813607; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FM4uBXU0Fe7orQha21mEGCioaWtdaQLN9aUonumnYDg=; b=A9oxmLiLjUT8/jNAZyoSuPAqTTzDcIcjWWBllOWMfM/iskuHMF/CDdadA+MpY1+Vr1KWGX BGhlAHtElxUGfiyOTr6mtfx5g0yvHcr2euAwFldpFBaKZgumzwTbZ98jn7FdcQhK+mF18O n2FvtZhSe/O8iuPGFCX3Kg9mwHK1x64= From: Lance Yang To: atomlin@atomlin.com Cc: akpm@linux-foundation.org, mhiramat@kernel.org, pmladek@suse.com, linux-kernel@vger.kernel.org, david.laight.linux@gmail.com, neelx@suse.com, sean@ashe.io, chjohnst@gmail.com, steve@abita.co, mproche@gmail.com, nick.lange@gmail.com, Lance Yang Subject: Re: [PATCH 2/2] hung_task: Always print basic hung task info header Date: Tue, 4 Aug 2026 11:19:59 +0800 Message-Id: <20260804031959.83680-1-lance.yang@linux.dev> In-Reply-To: <20260804001542.249639-3-atomlin@atomlin.com> References: <20260804001542.249639-3-atomlin@atomlin.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT On Mon, Aug 03, 2026 at 08:15:42PM -0400, Aaron Tomlin wrote: >From: Petr Mladek > >Currently, hung_task_info() completely suppresses any warning messages >once the warning budget is reached. This leaves the system completely >blind to any future hung tasks, even though we only wanted to suppress >heavy process stack dumps. > >Modify hung_task_info() to always print the basic single-line error message >about a hung task, regardless of whether the warning budget has been >exhausted. Restrict only the verbose details (such as stack dumps, >taint/release status, and blockers) to when the warning budget is intact >or panic is triggered. > >Additionally, update the notice printed upon warning exhaustion to clarify >that future reports will only omit process details rather than being completely >suppressed. > >Assisted-by: gemini-3.5-flash >Signed-off-by: Petr Mladek >--- Reviewed-by: Lance Yang