Re: Fw: [PATCHSET] workqueue: Show the latest workqueue name in /proc/PID/{comm,stat,status}

On Thu, May 17, 2018 at 12:51 AM Alexey Dobriyan wrote: > I'd say anything that extends ->comm past 16 charactes is no-no. > The reason is that userspace may do something stupid like: > char comm[16]; Not may - does. We're already talking to the procps-ng people

Re: Fw: [PATCHSET] workqueue: Show the latest workqueue name in /proc/PID/{comm,stat,status}

On Thu, May 17, 2018 at 12:51 AM Alexey Dobriyan wrote: > I'd say anything that extends ->comm past 16 charactes is no-no. > The reason is that userspace may do something stupid like: > char comm[16]; Not may - does. We're already talking to the procps-ng people exactly because of

Re: Fw: [PATCHSET] workqueue: Show the latest workqueue name in /proc/PID/{comm,stat,status}

.@linux-foundation.org, jiangshan...@gmail.com, > a...@linux-foundation.org > Cc: linux-kernel@vger.kernel.org, linux-...@vger.kernel.org, > kernel-t...@fb.com, csm...@enc.com.au > Subject: [PATCHSET] workqueue: Show the latest workqueue name in > /proc/PID/{comm,stat,status}

Re: Fw: [PATCHSET] workqueue: Show the latest workqueue name in /proc/PID/{comm,stat,status}

org, jiangshan...@gmail.com, > a...@linux-foundation.org > Cc: linux-kernel@vger.kernel.org, linux-...@vger.kernel.org, > kernel-t...@fb.com, csm...@enc.com.au > Subject: [PATCHSET] workqueue: Show the latest workqueue name in > /proc/PID/{comm,stat,status} > > > There can

[PATCHSET] workqueue: Show the latest workqueue name in /proc/PID/{comm,stat,status}

There can be a lot of workqueue workers and they all show up with the cryptic kworker/* names making it difficult to understand which is doing what and how they came to be. # ps -ef | grep kworker root 4 2 0 Feb25 ?00:00:00 [kworker/0:0H] root 6 2 0

[PATCHSET] workqueue: Show the latest workqueue name in /proc/PID/{comm,stat,status}

There can be a lot of workqueue workers and they all show up with the cryptic kworker/* names making it difficult to understand which is doing what and how they came to be. # ps -ef | grep kworker root 4 2 0 Feb25 ?00:00:00 [kworker/0:0H] root 6 2 0