public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC PATCH bpf-next 11/17] bpf: Add support to create tracing multi link
Date: Tue, 9 Aug 2022 10:50:35 +0800	[thread overview]
Message-ID: <202208091059.te2QbOWA-lkp@intel.com> (raw)
In-Reply-To: <20220808140626.422731-12-jolsa@kernel.org>

Hi Jiri,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on bpf/master]
[also build test ERROR on next-20220808]
[cannot apply to bpf-next/master rostedt-trace/for-next linus/master v5.19]
[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/Jiri-Olsa/bpf-Add-tracing-multi-link/20220808-221246
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
config: x86_64-randconfig-a011-20220808 (https://download.01.org/0day-ci/archive/20220809/202208091059.te2QbOWA-lkp@intel.com/config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 5f1c7e2cc5a3c07cbc2412e851a7283c1841f520)
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
        # https://github.com/intel-lab-lkp/linux/commit/c16f49e680e78a8df8ffc125e001217fb8be8e0b
        git remote add linux-review https://github.com/intel-lab-lkp/linux
        git fetch --no-tags linux-review Jiri-Olsa/bpf-Add-tracing-multi-link/20220808-221246
        git checkout c16f49e680e78a8df8ffc125e001217fb8be8e0b
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/i915/

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

All errors (new ones prefixed by >>):

   In file included from drivers/gpu/drm/i915/i915_trace_points.c:13:
   In file included from include/trace/../../drivers/gpu/drm/i915/i915_trace.h:770:
   In file included from include/trace/define_trace.h:102:
   In file included from include/trace/trace_events.h:21:
>> include/linux/trace_events.h:797:5: error: no previous prototype for function 'bpf_tracing_multi_attach' [-Werror,-Wmissing-prototypes]
   int bpf_tracing_multi_attach(struct bpf_prog *prog, const union bpf_attr *attr)
       ^
   include/linux/trace_events.h:797:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   int bpf_tracing_multi_attach(struct bpf_prog *prog, const union bpf_attr *attr)
   ^
   static 
   1 error generated.


vim +/bpf_tracing_multi_attach +797 include/linux/trace_events.h

   764	
   765	static inline int
   766	perf_event_query_prog_array(struct perf_event *event, void __user *info)
   767	{
   768		return -EOPNOTSUPP;
   769	}
   770	static inline int bpf_probe_register(struct bpf_raw_event_map *btp, struct bpf_prog *p)
   771	{
   772		return -EOPNOTSUPP;
   773	}
   774	static inline int bpf_probe_unregister(struct bpf_raw_event_map *btp, struct bpf_prog *p)
   775	{
   776		return -EOPNOTSUPP;
   777	}
   778	static inline struct bpf_raw_event_map *bpf_get_raw_tracepoint(const char *name)
   779	{
   780		return NULL;
   781	}
   782	static inline void bpf_put_raw_tracepoint(struct bpf_raw_event_map *btp)
   783	{
   784	}
   785	static inline int bpf_get_perf_event_info(const struct perf_event *event,
   786						  u32 *prog_id, u32 *fd_type,
   787						  const char **buf, u64 *probe_offset,
   788						  u64 *probe_addr)
   789	{
   790		return -EOPNOTSUPP;
   791	}
   792	static inline int
   793	bpf_kprobe_multi_link_attach(const union bpf_attr *attr, struct bpf_prog *prog)
   794	{
   795		return -EOPNOTSUPP;
   796	}
 > 797	int bpf_tracing_multi_attach(struct bpf_prog *prog, const union bpf_attr *attr)
   798	{
   799		return -EOPNOTSUPP;
   800	}
   801	#endif
   802	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

      parent reply	other threads:[~2022-08-09  2:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220808140626.422731-12-jolsa@kernel.org>
2022-08-09  1:18 ` [RFC PATCH bpf-next 11/17] bpf: Add support to create tracing multi link kernel test robot
2022-08-09  2:50 ` kernel test robot [this message]

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=202208091059.te2QbOWA-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jolsa@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    /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