linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Tom Zanussi <zanussi@kernel.org>,
	Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
	Yordan Karadzhov <y.karadz@gmail.com>
Subject: Re: [PATCH] tracing: Fix event probe removal from dynamic events
Date: Tue, 12 Oct 2021 14:49:49 +0800	[thread overview]
Message-ID: <202110121423.x2xd94xu-lkp@intel.com> (raw)
In-Reply-To: <20211011211105.48b6a5fd@oasis.local.home>

[-- Attachment #1: Type: text/plain, Size: 3842 bytes --]

Hi Steven,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on linux/master]
[also build test ERROR on hnaz-mm/master linus/master v5.15-rc5 next-20211011]
[cannot apply to tip/perf/core]
[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]

url:    https://github.com/0day-ci/linux/commits/Steven-Rostedt/tracing-Fix-event-probe-removal-from-dynamic-events/20211012-091238
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 5816b3e6577eaa676ceb00a848f0fd65fe2adc29
config: arm64-randconfig-r005-20211011 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c3dcf39554dbea780d6cb7e12239451ba47a2668)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://github.com/0day-ci/linux/commit/4d930af6a4aa75558017f921e2c9692ed27b2c56
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Steven-Rostedt/tracing-Fix-event-probe-removal-from-dynamic-events/20211012-091238
        git checkout 4d930af6a4aa75558017f921e2c9692ed27b2c56
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash kernel/trace/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> kernel/trace/trace_eprobe.c:128:2: error: use of undeclared identifier 'slash'
           slash = strchr(argv[0], '/');
           ^
   kernel/trace/trace_eprobe.c:129:7: error: use of undeclared identifier 'slash'
           if (!slash)
                ^
   kernel/trace/trace_eprobe.c:130:3: error: use of undeclared identifier 'slash'
                   slash = strchr(argv[0], '.');
                   ^
   kernel/trace/trace_eprobe.c:131:7: error: use of undeclared identifier 'slash'
           if (!slash)
                ^
   kernel/trace/trace_eprobe.c:134:41: error: use of undeclared identifier 'slash'
           if (strncmp(ep->event_system, argv[0], slash - argv[0]))
                                                  ^
   kernel/trace/trace_eprobe.c:136:29: error: use of undeclared identifier 'slash'
           if (strcmp(ep->event_name, slash + 1))
                                      ^
   6 errors generated.


vim +/slash +128 kernel/trace/trace_eprobe.c

   117	
   118	static bool eprobe_dyn_event_match(const char *system, const char *event,
   119				int argc, const char **argv, struct dyn_event *ev)
   120	{
   121		struct trace_eprobe *ep = to_trace_eprobe(ev);
   122	
   123		/* First argument is the system/event the probe is attached to */
   124	
   125		if (argc < 1)
   126			return false;
   127	
 > 128		slash = strchr(argv[0], '/');
   129		if (!slash)
   130			slash = strchr(argv[0], '.');
   131		if (!slash)
   132			return false;
   133	
   134		if (strncmp(ep->event_system, argv[0], slash - argv[0]))
   135			return false;
   136		if (strcmp(ep->event_name, slash + 1))
   137			return false;
   138	
   139		argc--;
   140		argv++;
   141	
   142		return strcmp(trace_probe_name(&ep->tp), event) == 0 &&
   143		    (!system || strcmp(trace_probe_group_name(&ep->tp), system) == 0) &&
   144		    trace_probe_match_command_args(&ep->tp, argc, argv);
   145	}
   146	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34308 bytes --]

       reply	other threads:[~2021-10-12  6:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211011211105.48b6a5fd@oasis.local.home>
2021-10-12  6:49 ` kernel test robot [this message]
2021-10-12 12:10   ` Steven Rostedt
2021-10-12  8:29 ` kernel test robot

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=202110121423.x2xd94xu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=llvm@lists.linux.dev \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tz.stoyanov@gmail.com \
    --cc=y.karadz@gmail.com \
    --cc=zanussi@kernel.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