From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC][PATCH] tracing: Allow creating instances with specified system events
Date: Tue, 28 Nov 2023 17:43:17 +0800 [thread overview]
Message-ID: <202311281631.XZ2umoXl-lkp@intel.com> (raw)
In-Reply-To: <20231127174108.3c331c9c@gandalf.local.home>
Hi Steven,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on jejb-scsi/for-next linus/master v6.7-rc3 next-20231128]
[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/Steven-Rostedt/tracing-Allow-creating-instances-with-specified-system-events/20231128-064317
base: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git for-next
patch link: https://lore.kernel.org/r/20231127174108.3c331c9c%40gandalf.local.home
patch subject: [RFC][PATCH] tracing: Allow creating instances with specified system events
config: i386-buildonly-randconfig-005-20231128 (https://download.01.org/0day-ci/archive/20231128/202311281631.XZ2umoXl-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231128/202311281631.XZ2umoXl-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/202311281631.XZ2umoXl-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/trace.c:9640: warning: Function parameter or member 'systems' not described in 'trace_array_get_by_name'
vim +9640 kernel/trace/trace.c
277ba04461c274 Steven Rostedt 2012-08-03 9622
28879787147358 Divya Indi 2019-11-20 9623 /**
28879787147358 Divya Indi 2019-11-20 9624 * trace_array_get_by_name - Create/Lookup a trace array, given its name.
28879787147358 Divya Indi 2019-11-20 9625 * @name: The name of the trace array to be looked up/created.
28879787147358 Divya Indi 2019-11-20 9626 *
28879787147358 Divya Indi 2019-11-20 9627 * Returns pointer to trace array with given name.
28879787147358 Divya Indi 2019-11-20 9628 * NULL, if it cannot be created.
28879787147358 Divya Indi 2019-11-20 9629 *
28879787147358 Divya Indi 2019-11-20 9630 * NOTE: This function increments the reference counter associated with the
28879787147358 Divya Indi 2019-11-20 9631 * trace array returned. This makes sure it cannot be freed while in use.
28879787147358 Divya Indi 2019-11-20 9632 * Use trace_array_put() once the trace array is no longer needed.
28394da2588816 Steven Rostedt (VMware 2020-01-24 9633) * If the trace_array is to be freed, trace_array_destroy() needs to
28394da2588816 Steven Rostedt (VMware 2020-01-24 9634) * be called after the trace_array_put(), or simply let user space delete
28394da2588816 Steven Rostedt (VMware 2020-01-24 9635) * it from the tracefs instances directory. But until the
28394da2588816 Steven Rostedt (VMware 2020-01-24 9636) * trace_array_put() is called, user space can not delete it.
28879787147358 Divya Indi 2019-11-20 9637 *
28879787147358 Divya Indi 2019-11-20 9638 */
d0f64c321316b8 Steven Rostedt (Google 2023-11-27 9639) struct trace_array *trace_array_get_by_name(const char *name, const char *systems)
f45d1225adb047 Divya Indi 2019-03-20 @9640 {
28879787147358 Divya Indi 2019-11-20 9641 struct trace_array *tr;
28879787147358 Divya Indi 2019-11-20 9642
28879787147358 Divya Indi 2019-11-20 9643 mutex_lock(&event_mutex);
28879787147358 Divya Indi 2019-11-20 9644 mutex_lock(&trace_types_lock);
28879787147358 Divya Indi 2019-11-20 9645
28879787147358 Divya Indi 2019-11-20 9646 list_for_each_entry(tr, &ftrace_trace_arrays, list) {
28879787147358 Divya Indi 2019-11-20 9647 if (tr->name && strcmp(tr->name, name) == 0)
28879787147358 Divya Indi 2019-11-20 9648 goto out_unlock;
28879787147358 Divya Indi 2019-11-20 9649 }
28879787147358 Divya Indi 2019-11-20 9650
d0f64c321316b8 Steven Rostedt (Google 2023-11-27 9651) tr = trace_array_create_systems(name, systems);
28879787147358 Divya Indi 2019-11-20 9652
28879787147358 Divya Indi 2019-11-20 9653 if (IS_ERR(tr))
28879787147358 Divya Indi 2019-11-20 9654 tr = NULL;
28879787147358 Divya Indi 2019-11-20 9655 out_unlock:
28879787147358 Divya Indi 2019-11-20 9656 if (tr)
28879787147358 Divya Indi 2019-11-20 9657 tr->ref++;
28879787147358 Divya Indi 2019-11-20 9658
28879787147358 Divya Indi 2019-11-20 9659 mutex_unlock(&trace_types_lock);
28879787147358 Divya Indi 2019-11-20 9660 mutex_unlock(&event_mutex);
28879787147358 Divya Indi 2019-11-20 9661 return tr;
277ba04461c274 Steven Rostedt 2012-08-03 9662 }
28879787147358 Divya Indi 2019-11-20 9663 EXPORT_SYMBOL_GPL(trace_array_get_by_name);
277ba04461c274 Steven Rostedt 2012-08-03 9664
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-28 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 22:41 [RFC][PATCH] tracing: Allow creating instances with specified system events Steven Rostedt
2023-11-27 22:50 ` Steven Rostedt
2023-11-28 8:49 ` Daniel Wagner
2023-11-28 9:43 ` kernel test robot [this message]
2023-11-28 14:21 ` Steven Rostedt
2023-11-28 13:14 ` Dmytro Maluka
2023-11-28 14:20 ` Steven Rostedt
2023-11-28 14:54 ` Steven Rostedt
2023-11-28 15:17 ` Masami Hiramatsu
2023-11-28 15:35 ` 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=202311281631.XZ2umoXl-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.