From: Aaron Tomlin <atomlin@atomlin.com>
To: akpm@linux-foundation.org, lance.yang@linux.dev,
mhiramat@kernel.org, gregkh@linuxfoundation.org,
pmladek@suse.com
Cc: sean@ashe.io, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] hung_task: Provide runtime reset interface for hung task detector
Date: Wed, 10 Dec 2025 22:30:02 -0500 [thread overview]
Message-ID: <20251211033004.1628875-1-atomlin@atomlin.com> (raw)
Hi Lance, Greg, Petr,
This series introduces the ability to reset
/proc/sys/kernel/hung_task_detect_count and consolidates hung
task warning into a single, atomic log block.
Writing any value to this file atomically resets the counter of detected
hung tasks to zero. This functionality provides system administrators with
the means to clear the cumulative diagnostic history following incident
resolution, thereby simplifying subsequent monitoring without necessitating
a system restart.
I intend to retain the use of the hung_task_diagnostics() helper function
to consolidate the multi-line logging logic for a detected hung task. The
primary goal is to improve code quality, readability, and ensure diagnostic
output integrity.
Please let me know your thoughts.
Changes since v1 [1]:
- Removed write-only sysfs attribute (Lance Yang)
- Modified procfs hung_task_detect_count instead (Lance Yang)
- Introduced a custom proc_handler
- Updated documentation (Lance Yang)
- Added 'static inline' as a hint to eliminate any function call overhead
- Removed clutter through encapsulation
[1]: https://lore.kernel.org/lkml/20251209041218.1583600-1-atomlin@atomlin.com/
Aaron Tomlin (2):
hung_task: Consolidate hung task warning into an atomic log block
hung_task: Enable runtime reset of hung_task_detect_count
Documentation/admin-guide/sysctl/kernel.rst | 2 +-
kernel/hung_task.c | 69 +++++++++++++++++----
2 files changed, 58 insertions(+), 13 deletions(-)
--
2.51.0
next reply other threads:[~2025-12-11 3:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 3:30 Aaron Tomlin [this message]
2025-12-11 3:30 ` [PATCH v2 1/2] hung_task: Consolidate hung task warning into an atomic log block Aaron Tomlin
2025-12-11 8:02 ` Greg KH
2025-12-15 23:44 ` Aaron Tomlin
2025-12-11 3:30 ` [PATCH v2 2/2] hung_task: Enable runtime reset of hung_task_detect_count Aaron Tomlin
2025-12-11 5:14 ` Lance Yang
2025-12-15 23:38 ` Aaron Tomlin
2025-12-11 15:49 ` kernel test robot
2025-12-15 5:00 ` kernel test robot
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=20251211033004.1628875-1-atomlin@atomlin.com \
--to=atomlin@atomlin.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=pmladek@suse.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox