[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250508095852.2d3f7e0b@gandalf.local.home>
Date: Thu, 8 May 2025 09:58:52 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Bhupesh Sharma <bhsharma@...lia.com>
Cc: Petr Mladek <pmladek@...e.com>, Bhupesh <bhupesh@...lia.com>,
akpm@...ux-foundation.org, kernel-dev@...lia.com,
linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
linux-perf-users@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, oliver.sang@...el.com, lkp@...el.com,
laoar.shao@...il.com, mathieu.desnoyers@...icios.com,
arnaldo.melo@...il.com, alexei.starovoitov@...il.com,
andrii.nakryiko@...il.com, mirq-linux@...e.qmqm.pl, peterz@...radead.org,
willy@...radead.org, david@...hat.com, viro@...iv.linux.org.uk,
keescook@...omium.org, ebiederm@...ssion.com, brauner@...nel.org,
jack@...e.cz, mingo@...hat.com, juri.lelli@...hat.com, bsegall@...gle.com,
mgorman@...e.de, vschneid@...hat.com
Subject: Re: [PATCH v3 3/3] exec: Add support for 64 byte 'tsk->real_comm'
On Thu, 8 May 2025 13:38:11 +0530
Bhupesh Sharma <bhsharma@...lia.com> wrote:
> >> something like:
> >>
> >> char comm_ext[TASK_COMM_EXT_LEN];
> >> or
> >> char comm_64[TASK_COMM_64_LEN]
> > I prefer "comm_ext" as I don't think we want to hard code the actual size.
> > Who knows, in the future we may extend it again!
> >
>
> Ok, let me use 'comm_64' instead in v4.
I think you missed what I said. I prefer the comm_ext over comm_64 because
I don't think it's a good idea to hardcode the extended size in the name.
That will make it very difficult in the future if we want to make it even
larger.
-- Steve
Powered by blists - more mailing lists