From: Tio Zhang <tiozhang@didiglobal.com>
To: <pmladek@suse.com>, <yu.c.chen@intel.com>
Cc: <juri.lelli@redhat.com>, <mingo@redhat.com>,
<peterz@infradead.org>, <vincent.guittot@linaro.org>,
<linux-kernel@vger.kernel.org>, <tiozhang@didiglobal.com>,
<zyhtheonly@gmail.com>, <zwp10758@gmail.com>,
<zyhtheonly@yeah.net>
Subject: [PATCH v2] sched: print parent comm in sched_show_task()
Date: Thu, 19 Jan 2023 19:06:42 +0800 [thread overview]
Message-ID: <20230119110642.GA6463@didi-ThinkCentre-M930t-N000> (raw)
Knowing who the parent is might be useful for debugging.
For example, we can sometimes resolve kernel hung tasks by stopping
the person who begins those hung tasks.
With the parent's name printed in sched_show_task(),
it might be helpful to let people know which "service" should be operated.
Also, we move the parent info to a following new line while keeping the
original line the same.
And we would print "parent:unknown ppid:<NULL>"
when the task is not alive.
Signed-off-by: Tio Zhang <tiozhang@didiglobal.com>
---
kernel/sched/core.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index cb2aa2b54c7a..5690a5700f9e 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -8854,6 +8854,7 @@ void sched_show_task(struct task_struct *p)
{
unsigned long free = 0;
int ppid;
+ char *pcomm = NULL;
if (!try_get_task_stack(p))
return;
@@ -8867,13 +8868,22 @@ void sched_show_task(struct task_struct *p)
#endif
ppid = 0;
rcu_read_lock();
- if (pid_alive(p))
- ppid = task_pid_nr(rcu_dereference(p->real_parent));
+ if (pid_alive(p)) {
+ struct task_struct *parent = rcu_dereference(p->real_parent);
+
+ ppid = task_pid_nr(parent);
+ pcomm = parent->comm;
+ }
rcu_read_unlock();
pr_cont(" stack:%-5lu pid:%-5d ppid:%-6d flags:0x%08lx\n",
free, task_pid_nr(p), ppid,
read_task_thread_flags(p));
+ if (!ppid)
+ pr_info("parent:unknown ppid:<NULL>\n");
+ else
+ pr_info("parent:%-15.15s ppid:%-6d\n", pcomm, ppid);
+
print_worker_info(KERN_INFO, p);
print_stop_info(KERN_INFO, p);
show_stack(p, NULL, KERN_INFO);
--
2.17.1
next reply other threads:[~2023-01-19 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 11:06 Tio Zhang [this message]
2023-01-20 13:09 ` Petr Mladek
2023-01-31 8:10 ` [PATCH v2 2/2] " Tio Zhang
2023-02-09 9:45 ` 张元瀚 Tio Zhang
2023-02-09 16:21 ` Chen Yu
[not found] ` <CAEQmJ=igQ8J9Y+_dWE6yaaFXHC965Sw+RxywWNLD=4G=tj0_hw@mail.gmail.com>
[not found] ` <CAEQmJ=iEC1G4MVRG=0XLWrCxqX_3E-6X-XbPeg8ti7oFjTBLBQ@mail.gmail.com>
2023-03-27 11:43 ` [RESEND][PATCH " Petr Mladek
2023-03-28 3:44 ` [PATCH v3] " Tio Zhang
2023-03-28 9:40 ` Petr Mladek
2023-06-02 5:44 ` [PATCH v3 2/2] " Tio Zhang
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=20230119110642.GA6463@didi-ThinkCentre-M930t-N000 \
--to=tiozhang@didiglobal.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=vincent.guittot@linaro.org \
--cc=yu.c.chen@intel.com \
--cc=zwp10758@gmail.com \
--cc=zyhtheonly@gmail.com \
--cc=zyhtheonly@yeah.net \
/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
all inboxes | Powered by JetHome®