[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250724091604.2336532-1-safinaskar@zohomail.com>
Date: Thu, 24 Jul 2025 12:16:04 +0300
From: Askar Safin <safinaskar@...omail.com>
To: bhupesh@...lia.com
Cc: akpm@...ux-foundation.org,
alexei.starovoitov@...il.com,
andrii.nakryiko@...il.com,
arnaldo.melo@...il.com,
bpf@...r.kernel.org,
brauner@...nel.org,
bsegall@...gle.com,
david@...hat.com,
ebiederm@...ssion.com,
jack@...e.cz,
juri.lelli@...hat.com,
kees@...nel.org,
keescook@...omium.org,
kernel-dev@...lia.com,
laoar.shao@...il.com,
linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-mm@...ck.org,
linux-perf-users@...r.kernel.org,
linux-trace-kernel@...r.kernel.org,
lkp@...el.com,
mathieu.desnoyers@...icios.com,
mgorman@...e.de,
mingo@...hat.com,
mirq-linux@...e.qmqm.pl,
oliver.sang@...el.com,
peterz@...radead.org,
pmladek@...e.com,
rostedt@...dmis.org,
torvalds@...ux-foundation.org,
viro@...iv.linux.org.uk,
vschneid@...hat.com,
willy@...radead.org
Subject: Re: [PATCH v5 3/3] treewide: Switch from tsk->comm to tsk->comm_str which is 64 bytes long
> where TASK_COMM_EXT_LEN is 64-bytes.
Why 64? As well as I understand, comm is initialized from executable file name by default. And it is usually limited by 256 (or 255?) bytes. So, please, make limit 256 bytes.
--
Askar Safin
Powered by blists - more mailing lists