All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: sean@ashe.io, linux-kernel@vger.kernel.org,
	akpm@linux-foundation.org, mhiramat@kernel.org,
	gregkh@linuxfoundation.org
Subject: Re: [PATCH 2/2] hung_task: Provide runtime reset interface for hung task detector
Date: Tue, 9 Dec 2025 12:54:14 +0800	[thread overview]
Message-ID: <700d4bae-0565-4eac-b609-073e9893286d@linux.dev> (raw)
In-Reply-To: <20251209041218.1583600-3-atomlin@atomlin.com>



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

  reply	other threads:[~2025-12-09  4:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09  4:12 [PATCH 0/2] hung_task: Provide runtime reset interface for hung task detector Aaron Tomlin
2025-12-09  4:12 ` [PATCH 1/2] hung_task: Consolidate hung task warning into an atomic log block Aaron Tomlin
2025-12-09  5:12   ` Lance Yang
2025-12-09  6:56     ` Greg KH
2025-12-09 22:14       ` Aaron Tomlin
2025-12-10  7:37         ` Greg KH
2025-12-10 13:08         ` Petr Mladek
2025-12-09 22:11     ` Aaron Tomlin
2025-12-09  4:12 ` [PATCH 2/2] hung_task: Provide runtime reset interface for hung task detector Aaron Tomlin
2025-12-09  4:54   ` Lance Yang [this message]
2025-12-09 22:06     ` Aaron Tomlin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=700d4bae-0565-4eac-b609-073e9893286d@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=atomlin@atomlin.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=sean@ashe.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.