From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-165.mta1.migadu.com (out-165.mta1.migadu.com [95.215.58.165]) (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 CCAEB4766B6 for ; Tue, 4 Aug 2026 16:43:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.165 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785861810; cv=none; b=dTSw4rTywLprq5SeqdnFsVC3DrYUSwa+33cGeq+1VVT+0tS7q8HYIupdu6vqm7ryxUpdcU/AdmqksNaYkOnqKOCYwodReLGIEMEQPdyTFP0nz2ayKGLN3GeOpwDFyQ74jwojrbX8/Tlq3Aq+i1q+2jOBaQiozzCaThdmUIj5DXE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785861810; c=relaxed/simple; bh=/zhEbdB0OgFqDb/RRCXaTxhZLz6sif9MStx/MYkbeZI=; h=From:To:Cc:Subject:Date:Message-Id:In-Reply-To:References: MIME-Version:Content-Type; b=c/+wGqF2kNQjShAuo+tJXVIeXz0pVfkeM6B927lrYHKXn6u3zmEBclHuKGLFyXsxNA8FDX1SgWtmQ7f91GHksp4STCI7NGbv+WAvNqO+PH5tJliquASS147HJl8KGLGrUuCSbTE4MvSQ3vNVmrQ7nYEVhNIYbA5R2BMXfTaYFEA= 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=QoSa+Wpa; arc=none smtp.client-ip=95.215.58.165 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="QoSa+Wpa" 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=1785861789; 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=/zhEbdB0OgFqDb/RRCXaTxhZLz6sif9MStx/MYkbeZI=; b=QoSa+WpaXi2NqyBbvaFwChdWm7+knViJwNSELryrDPQGkHzG5F7+l86R8v7URIAWvpoj7h G///2F8Dh4UqJq0F4nJlanahxCq7jtf1V/dWYE123RAt+2pjghxqceZIG3MUfDSPUS/gcc t2ZitykkADjIOOZR6iho6WhA1JAYgfE= 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 v7 2/2] hung_task: Always print basic hung task info header Date: Wed, 5 Aug 2026 00:42:51 +0800 Message-Id: <20260804164251.81206-1-lance.yang@linux.dev> In-Reply-To: <20260804155406.254810-3-atomlin@atomlin.com> References: <20260804155406.254810-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 Tue, Aug 04, 2026 at 11:54:06AM -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. I'd keep it simple and go with: " hung_task: always print the blocked-task line Once the warning budget is exhausted, hung_task_info() stops printing any per-task message. Detection still increments hung_task_detect_count and emits trace_sched_process_hang(), but dmesg no longer shows which task is blocked. Move the "INFO: task ... blocked" line outside the budget check. Keep the rest of the per-task report budgeted and update the exhaustion message accordingly. " [...] Cheers, Lance