linux-kernel - Re: [PATCH v2 2/2] sched: print parent comm in sched_show

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Y+UdoShroyR3iynv@chenyu5-mobl1>
Date:   Fri, 10 Feb 2023 00:21:53 +0800
From:   Chen Yu <yu.c.chen@...el.com>
To:     <pmladek@...e.com>, <juri.lelli@...hat.com>, <mingo@...hat.com>,
        <peterz@...radead.org>, <vincent.guittot@...aro.org>,
        <linux-kernel@...r.kernel.org>, <zyhtheonly@...il.com>,
        <zwp10758@...il.com>, <zyhtheonly@...h.net>
Subject: Re: [PATCH v2 2/2] sched: print parent comm in sched_show_task()

On 2023-01-31 at 16:10:26 +0800, Tio Zhang wrote:
> 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.
> It would better solve the situation when the task
s/would better/would be better/
> is not alive and we could not get information about the parent.
> 
> Signed-off-by: Tio Zhang <tiozhang@...iglobal.com>
>
Looks ok to me,
Tested-by: Chen Yu <yu.c.chen@...el.com> 

thanks,
Chenyu