All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [jolsa-perf:bpf/ftrace 3/7] kernel/bpf/syscall.c:2937:3: error: implicit declaration of function 'bpf_trace_run2'
Date: Wed, 14 Apr 2021 01:18:49 +0800	[thread overview]
Message-ID: <202104140144.xkQ9LcA0-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git bpf/ftrace
head:   75bc48cb4414f68f3a427d021860af113920adfd
commit: a1f1f141147a15afbfcc897661c59e23285f941a [3/7] bpf: Add support to attach program to ftrace probe
config: powerpc64-randconfig-r016-20210413 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 9829f5e6b1bca9b61efc629770d28bb9014dec45)
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 powerpc64 cross compiling tool for clang build
        # apt-get install binutils-powerpc64-linux-gnu
        # https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git/commit/?id=a1f1f141147a15afbfcc897661c59e23285f941a
        git remote add jolsa-perf https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
        git fetch --no-tags jolsa-perf bpf/ftrace
        git checkout a1f1f141147a15afbfcc897661c59e23285f941a
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=powerpc64 

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/bpf/syscall.c:2937:3: error: implicit declaration of function 'bpf_trace_run2' [-Werror,-Wimplicit-function-declaration]
                   bpf_trace_run2(tr_link->link.prog, ip, parent_ip);
                   ^
   1 error generated.


vim +/bpf_trace_run2 +2937 kernel/bpf/syscall.c

  2919	
  2920	static void
  2921	bpf_ftrace_function_call(unsigned long ip, unsigned long parent_ip,
  2922				 struct ftrace_ops *ops,  struct ftrace_regs *fregs)
  2923	{
  2924		struct bpf_tracing_ftrace_link *tr_link;
  2925		struct bpf_prog *prog;
  2926		u64 start;
  2927	
  2928		tr_link = container_of(ops, struct bpf_tracing_ftrace_link, ops);
  2929		prog = tr_link->link.prog;
  2930	
  2931		if (prog->aux->sleepable)
  2932			start = __bpf_prog_enter_sleepable(prog);
  2933		else
  2934			start = __bpf_prog_enter(prog);
  2935	
  2936		if (start)
> 2937			bpf_trace_run2(tr_link->link.prog, ip, parent_ip);
  2938	
  2939		if (prog->aux->sleepable)
  2940			__bpf_prog_exit_sleepable(prog, start);
  2941		else
  2942			__bpf_prog_exit(prog, start);
  2943	}
  2944	

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

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

             reply	other threads:[~2021-04-13 17:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 17:18 kernel test robot [this message]
2021-04-14 23:56 [jolsa-perf:bpf/ftrace 3/7] kernel/bpf/syscall.c:2937:3: error: implicit declaration of function 'bpf_trace_run2' 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=202104140144.xkQ9LcA0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.