Thread (33 messages) 33 messages, 8 authors, 2021-11-18

Re: [PATCH v7 00/11] extend task comm from 16 to 24

From: Steven Rostedt <rostedt@goodmis.org>
Date: 2021-11-01 16:06:48
Also in: bpf, linux-fsdevel, linux-mm, linux-perf-users, linux-rdma, lkml

On Mon, 1 Nov 2021 17:02:12 +0100
Petr Mladek [off-list ref] wrote:
quoted
I thought Steven[1] and  Kees[2] have already clearly explained why we
do it like that, so I didn't give any more words on it.

[1]. https://lore.kernel.org/all/20211025170503.59830a43@gandalf.local.home/ (local)  
Steven was against switching task->comm[16] into a dynamically
allocated pointer. But he was not against storing longer names
separately.
Just to be clear. I was recommending that the comm[16] would still behave
like it does today. Where it is truncated. But if the name is longer, it
could be stored in a separate location if the caller wanted to know the
full name.

-- Steve
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help