linux-kernel - Re: [PATCH] tracing: Report wrong dynamic event command

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <202511092149.N375MBPu-lkp@intel.com>
Date: Sun, 9 Nov 2025 21:27:50 +0800
From: kernel test robot <lkp@...el.com>
To: "Masami Hiramatsu (Google)" <mhiramat@...nel.org>,
	Steven Rostedt <rostedt@...dmis.org>
Cc: oe-kbuild-all@...ts.linux.dev,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing: Report wrong dynamic event command

Hi Masami,

kernel test robot noticed the following build errors:

[auto build test ERROR on trace/for-next]
[also build test ERROR on next-20251107]
[cannot apply to linus/master v6.18-rc4]
[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/Masami-Hiramatsu-Google/tracing-Report-wrong-dynamic-event-command/20251108-185823
base:   https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link:    https://lore.kernel.org/r/176259938768.261465.10714633393722227911.stgit%40devnote2
patch subject: [PATCH] tracing: Report wrong dynamic event command
config: s390-randconfig-002-20251109 (https://download.01.org/0day-ci/archive/20251109/202511092149.N375MBPu-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251109/202511092149.N375MBPu-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@...el.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202511092149.N375MBPu-lkp@intel.com/

All errors (new ones prefixed by >>):

   s390-linux-ld: kernel/trace/trace_dynevent.o: in function `create_dyn_event':
>> kernel/trace/trace_dynevent.c:150: undefined reference to `trace_probe_log_init'
>> s390-linux-ld: kernel/trace/trace_dynevent.c:151: undefined reference to `__trace_probe_log_err'
>> s390-linux-ld: kernel/trace/trace_dynevent.c:152: undefined reference to `trace_probe_log_clear'

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for I2C_K1
   Depends on [n]: I2C [=y] && HAS_IOMEM [=y] && (ARCH_SPACEMIT || COMPILE_TEST [=y]) && OF [=n]
   Selected by [y]:
   - MFD_SPACEMIT_P1 [=y] && HAS_IOMEM [=y] && (ARCH_SPACEMIT || COMPILE_TEST [=y]) && I2C [=y]


vim +150 kernel/trace/trace_dynevent.c

   133	
   134	static int create_dyn_event(const char *raw_command)
   135	{
   136		struct dyn_event_operations *ops;
   137		int ret = -ENODEV;
   138	
   139		if (raw_command[0] == '-' || raw_command[0] == '!')
   140			return dyn_event_release(raw_command, NULL);
   141	
   142		mutex_lock(&dyn_event_ops_mutex);
   143		list_for_each_entry(ops, &dyn_event_ops_list, list) {
   144			ret = ops->create(raw_command);
   145			if (!ret || ret != -ECANCELED)
   146				break;
   147		}
   148		if (ret == -ECANCELED) {
   149			/* Wrong dynamic event. Leave an error message. */
 > 150			trace_probe_log_init("dynevent", 1, &raw_command);
 > 151			trace_probe_log_err(0, BAD_DYN_EVENT);
 > 152			trace_probe_log_clear();
   153			ret = -EINVAL;
   154		}
   155	
   156		mutex_unlock(&dyn_event_ops_mutex);
   157	
   158		return ret;
   159	}
   160	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki