From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-183.mta0.migadu.com (out-183.mta0.migadu.com [91.218.175.183]) (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 EF31179DA for ; Tue, 9 Dec 2025 04:54:21 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.183 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765256064; cv=none; b=NarSmZoqojLtiVIDCrpXSvH8OuV7aq8Etz2S0ovgyP27/ToXJqO92jrPWVIK0k5r69FNeVqqqMO3rts1bMSvvbbnf/5EMjO3PuWmgAbhp7IIdF2LDk72LUmqpzbwvPqitCPcPoBS/4Km0J8PGoGJRsjkctfuuWVRInU2QqJRYrE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765256064; c=relaxed/simple; bh=di8LuuHUUDt8SSPI53WsJwFi16ApqwV4peYhkupAsC0=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=FV12eHCjX7LA8Qa8PleINxJl9jRmR8/fvHSQUPa3im8IZMGAOE9otIKtoM39TtaF1yQqTx32gqdeAkh917wBXll6d/lbNelya0oHWMPlm1ZmlNmu20PBTnb7B2ZqEuvzOXOs6vZ7n3+dcCeg6UiA7mDR1c8wl9fozqtReFVnzZI= 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=Y+QuuAm8; arc=none smtp.client-ip=91.218.175.183 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="Y+QuuAm8" Message-ID: <700d4bae-0565-4eac-b609-073e9893286d@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1765256059; 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=di8LuuHUUDt8SSPI53WsJwFi16ApqwV4peYhkupAsC0=; b=Y+QuuAm8Cn0LplG3c8rQan6bkuSSu9EYgRhEs6BVqS9sTNf/uhwBSpheyUmPh+JkoVl3wn f5ReIfkMFl8Kf7q8raMFugJgLXzSOIKLw1pMPfjjeOVOM2VXVHTdI423jjZ7KEM9iJCThg W4mnEo6txMS63HdcUgUdnbkmgCiiNOQ= Date: Tue, 9 Dec 2025 12:54:14 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH 2/2] hung_task: Provide runtime reset interface for hung task detector To: Aaron Tomlin Cc: sean@ashe.io, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, mhiramat@kernel.org, gregkh@linuxfoundation.org References: <20251209041218.1583600-1-atomlin@atomlin.com> <20251209041218.1583600-3-atomlin@atomlin.com> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Lance Yang In-Reply-To: <20251209041218.1583600-3-atomlin@atomlin.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 2025/12/9 12:12, Aaron Tomlin wrote: > This patch introduces a new write-only sysfs file, > hung_task_detect_count_reset, directly under /sys/kernel/. > This file exposes an explicit control point for resetting the > /proc/sys/kernel/hung_task_detect_count counter. Is the new file really necessary? I'd perfer if we just made the existing hung_task_detect_count writable ;) Just let users echo 0 (or anything) to reset it, and make sure to update the documentation as well. Cheers, Lance