From: Petr Mladek <pmladek@suse.com>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lance Yang <ioworker0@gmail.com>,
paulmck@kernel.org, Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] hung_task: Add hung_task_sys_info sysctl to dump sys info on task-hung
Date: Wed, 12 Nov 2025 15:44:09 +0100 [thread overview]
Message-ID: <aRSdOfA3bgvCzdfH@pathway.suse.cz> (raw)
In-Reply-To: <aRRupyzGaP5Z35qE@U-2FWC9VHC-2323.local>
On Wed 2025-11-12 19:25:27, Feng Tang wrote:
> On Mon, Nov 10, 2025 at 06:55:57PM +0100, Petr Mladek wrote:
> > On Thu 2025-11-06 10:30:31, Feng Tang wrote:
> [...]
> > @@ -315,8 +295,10 @@ static void check_hung_uninterruptible_tasks(unsigned long timeout)
> > {
> > int max_count = sysctl_hung_task_check_count;
> > unsigned long last_break = jiffies;
> > + unsigned long total_hung_task;
> > struct task_struct *g, *t;
> > unsigned long prev_detect_count = sysctl_hung_task_detect_count;
> > + unsigned long si_mask;
> >
> > /*
> > * If the system crashed already then all bets are off,
> > @@ -325,6 +307,14 @@ static void check_hung_uninterruptible_tasks(unsigned long timeout)
> > if (test_taint(TAINT_DIE) || did_panic)
> > return;
> >
> > + si_mask = hung_task_si_mask;
> > + if (sysctl_hung_task_warnings || hung_task_call_panic) {
> > + si_mask |= SYS_INFO_LOCKS;
> > +
> > + if (sysctl_hung_task_all_cpu_backtrace)
> > + si_mask |= SYS_INFO_ALL_BT;
> > + }
>
> This probably needs to be moved to after the loop check of
> check_hung_task().
I did it on purpose because "sysctl_hung_task_warnings" might get
decremented down to "0" in the loop below. But IMHO, we need to print
the information if it was non-zero at the beginning.
It might be worth to add a comment why it has to be done
before the cycle.
> > +
> > rcu_read_lock();
> > for_each_process_thread(g, t) {
> >
Best Regards,
Petr
next prev parent reply other threads:[~2025-11-12 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 2:30 [PATCH 0/3] Enable hung_task and lockup cases to dump system info on demand Feng Tang
2025-11-06 2:30 ` [PATCH 1/3] docs: panic: correct some sys_ifo names in sysctl doc Feng Tang
2025-11-10 16:52 ` Petr Mladek
2025-11-11 14:09 ` Feng Tang
2025-11-06 2:30 ` [PATCH 2/3] hung_task: Add hung_task_sys_info sysctl to dump sys info on task-hung Feng Tang
2025-11-06 3:28 ` Lance Yang
2025-11-06 4:48 ` Feng Tang
2025-11-10 17:55 ` Petr Mladek
2025-11-11 13:37 ` Feng Tang
2025-11-12 11:25 ` Feng Tang
2025-11-12 14:44 ` Petr Mladek [this message]
2025-11-13 2:56 ` Feng Tang
2025-11-06 2:30 ` [PATCH 3/3] watchdog: add lockup_sys_info sysctl to dump sys info on system lockup Feng Tang
2025-11-11 13:26 ` Petr Mladek
2025-11-11 14:09 ` Feng Tang
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=aRSdOfA3bgvCzdfH@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@linux.alibaba.com \
--cc=ioworker0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rostedt@goodmis.org \
/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