From: kernel test robot <lkp@intel.com>
To: Bhupesh <bhupesh@igalia.com>, akpm@linux-foundation.org
Cc: oe-kbuild-all@lists.linux.dev, bhupesh@igalia.com,
kernel-dev@igalia.com, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
oliver.sang@intel.com, lkp@intel.com, laoar.shao@gmail.com,
pmladek@suse.com, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, arnaldo.melo@gmail.com,
alexei.starovoitov@gmail.com, andrii.nakryiko@gmail.com,
mirq-linux@rere.qmqm.pl, peterz@infradead.org,
willy@infradead.org, david@redhat.com, viro@zeniv.linux.org.uk,
keescook@chromium.org, ebiederm@xmission.com, brauner@kernel.org,
jack@suse.cz, mingo@redhat.com, juri.lelli@redhat.com,
bsegall@google.com, mgorman@suse.de
Subject: Re: [PATCH v3 2/3] treewide: Switch memcpy() users of 'task->comm' to a more safer implementation
Date: Thu, 8 May 2025 20:21:32 +0800 [thread overview]
Message-ID: <202505082038.A5ejhbR4-lkp@intel.com> (raw)
In-Reply-To: <20250507110444.963779-3-bhupesh@igalia.com>
Hi Bhupesh,
kernel test robot noticed the following build errors:
[auto build test ERROR on trace/for-next]
[also build test ERROR on tip/sched/core akpm-mm/mm-everything linus/master v6.15-rc5 next-20250508]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Bhupesh/exec-Remove-obsolete-comments/20250507-190740
base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link: https://lore.kernel.org/r/20250507110444.963779-3-bhupesh%40igalia.com
patch subject: [PATCH v3 2/3] treewide: Switch memcpy() users of 'task->comm' to a more safer implementation
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20250508/202505082038.A5ejhbR4-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250508/202505082038.A5ejhbR4-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202505082038.A5ejhbR4-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from include/trace/define_trace.h:119,
from include/trace/events/sched.h:856,
from kernel/sched/core.c:84:
include/trace/events/sched.h: In function 'do_trace_event_raw_event_sched_switch':
>> include/trace/events/sched.h:245:24: error: 'struct trace_event_raw_sched_switch' has no member named 'comm'
245 | __entry->comm[TASK_COMM_LEN - 1] = '\0';
| ^~
include/trace/trace_events.h:427:11: note: in definition of macro '__DECLARE_EVENT_CLASS'
427 | { assign; } \
| ^~~~~~
include/trace/trace_events.h:435:23: note: in expansion of macro 'PARAMS'
435 | PARAMS(assign), PARAMS(print)) \
| ^~~~~~
include/trace/trace_events.h:40:9: note: in expansion of macro 'DECLARE_EVENT_CLASS'
40 | DECLARE_EVENT_CLASS(name, \
| ^~~~~~~~~~~~~~~~~~~
include/trace/trace_events.h:44:30: note: in expansion of macro 'PARAMS'
44 | PARAMS(assign), \
| ^~~~~~
include/trace/events/sched.h:224:1: note: in expansion of macro 'TRACE_EVENT'
224 | TRACE_EVENT(sched_switch,
| ^~~~~~~~~~~
include/trace/events/sched.h:243:9: note: in expansion of macro 'TP_fast_assign'
243 | TP_fast_assign(
| ^~~~~~~~~~~~~~
In file included from include/trace/define_trace.h:120,
from include/trace/events/sched.h:856,
from kernel/sched/core.c:84:
include/trace/events/sched.h: In function 'do_perf_trace_sched_switch':
>> include/trace/events/sched.h:245:24: error: 'struct trace_event_raw_sched_switch' has no member named 'comm'
245 | __entry->comm[TASK_COMM_LEN - 1] = '\0';
| ^~
include/trace/perf.h:51:11: note: in definition of macro '__DECLARE_EVENT_CLASS'
51 | { assign; } \
| ^~~~~~
include/trace/perf.h:67:23: note: in expansion of macro 'PARAMS'
67 | PARAMS(assign), PARAMS(print)) \
| ^~~~~~
include/trace/trace_events.h:40:9: note: in expansion of macro 'DECLARE_EVENT_CLASS'
40 | DECLARE_EVENT_CLASS(name, \
| ^~~~~~~~~~~~~~~~~~~
include/trace/trace_events.h:44:30: note: in expansion of macro 'PARAMS'
44 | PARAMS(assign), \
| ^~~~~~
include/trace/events/sched.h:224:1: note: in expansion of macro 'TRACE_EVENT'
224 | TRACE_EVENT(sched_switch,
| ^~~~~~~~~~~
include/trace/events/sched.h:243:9: note: in expansion of macro 'TP_fast_assign'
243 | TP_fast_assign(
| ^~~~~~~~~~~~~~
vim +245 include/trace/events/sched.h
225
226 TP_PROTO(bool preempt,
227 struct task_struct *prev,
228 struct task_struct *next,
229 unsigned int prev_state),
230
231 TP_ARGS(preempt, prev, next, prev_state),
232
233 TP_STRUCT__entry(
234 __array( char, prev_comm, TASK_COMM_LEN )
235 __field( pid_t, prev_pid )
236 __field( int, prev_prio )
237 __field( long, prev_state )
238 __array( char, next_comm, TASK_COMM_LEN )
239 __field( pid_t, next_pid )
240 __field( int, next_prio )
241 ),
242
243 TP_fast_assign(
244 memcpy(__entry->prev_comm, prev->comm, TASK_COMM_LEN);
> 245 __entry->comm[TASK_COMM_LEN - 1] = '\0';
246 __entry->prev_pid = prev->pid;
247 __entry->prev_prio = prev->prio;
248 __entry->prev_state = __trace_sched_switch_state(preempt, prev_state, prev);
249 memcpy(__entry->next_comm, next->comm, TASK_COMM_LEN);
250 __entry->next_comm[TASK_COMM_LEN - 1] = '\0';
251 __entry->next_pid = next->pid;
252 __entry->next_prio = next->prio;
253 /* XXX SCHED_DEADLINE */
254 ),
255
256 TP_printk("prev_comm=%s prev_pid=%d prev_prio=%d prev_state=%s%s ==> next_comm=%s next_pid=%d next_prio=%d",
257 __entry->prev_comm, __entry->prev_pid, __entry->prev_prio,
258
259 (__entry->prev_state & (TASK_REPORT_MAX - 1)) ?
260 __print_flags(__entry->prev_state & (TASK_REPORT_MAX - 1), "|",
261 { TASK_INTERRUPTIBLE, "S" },
262 { TASK_UNINTERRUPTIBLE, "D" },
263 { __TASK_STOPPED, "T" },
264 { __TASK_TRACED, "t" },
265 { EXIT_DEAD, "X" },
266 { EXIT_ZOMBIE, "Z" },
267 { TASK_PARKED, "P" },
268 { TASK_DEAD, "I" }) :
269 "R",
270
271 __entry->prev_state & TASK_REPORT_MAX ? "+" : "",
272 __entry->next_comm, __entry->next_pid, __entry->next_prio)
273 );
274
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-08 12:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 11:04 [PATCH v3 0/3] Add support for long task name Bhupesh
2025-05-07 11:04 ` [PATCH v3 1/3] exec: Remove obsolete comments Bhupesh
2025-05-07 11:04 ` [PATCH v3 2/3] treewide: Switch memcpy() users of 'task->comm' to a more safer implementation Bhupesh
2025-05-07 12:29 ` Petr Mladek
2025-05-08 8:17 ` Bhupesh Sharma
2025-05-08 8:22 ` Bhupesh Sharma
2025-05-08 14:02 ` Steven Rostedt
2025-05-08 12:21 ` kernel test robot [this message]
2025-05-07 11:04 ` [PATCH v3 3/3] exec: Add support for 64 byte 'tsk->real_comm' Bhupesh
2025-05-07 12:54 ` Petr Mladek
2025-05-07 17:23 ` Steven Rostedt
2025-05-08 8:08 ` Bhupesh Sharma
2025-05-08 13:58 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202505082038.A5ejhbR4-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=bhupesh@igalia.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=bsegall@google.com \
--cc=david@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jack@suse.cz \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=kernel-dev@igalia.com \
--cc=laoar.shao@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=mirq-linux@rere.qmqm.pl \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox