All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ast:bpf_tramp 4/6] kernel/bpf/verifier.c:9485:40: error: 'MCOUNT_INSN_SIZE' undeclared; did you mean 'UCOUNT_COUNTS'?
Date: Thu, 31 Oct 2019 11:00:40 +0800	[thread overview]
Message-ID: <201910311139.e6PLPOcc%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/ast/bpf.git bpf_tramp
head:   79342704f7a85cae631373124998449f047fa0f1
commit: 1d5c082bc909135b1e206a34e0cfcd57d29dbd62 [4/6] bpf: introduce BPF trampoline
config: m68k-allyesconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 1d5c082bc909135b1e206a34e0cfcd57d29dbd62
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=m68k 

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

All errors (new ones prefixed by >>):

   kernel/bpf/verifier.c: In function 'prepare_bpf_trampoline':
>> kernel/bpf/verifier.c:9485:40: error: 'MCOUNT_INSN_SIZE' undeclared (first use in this function); did you mean 'UCOUNT_COUNTS'?
             prog->aux->attach_func_addr + MCOUNT_INSN_SIZE);
                                           ^~~~~~~~~~~~~~~~
                                           UCOUNT_COUNTS
   kernel/bpf/verifier.c:9485:40: note: each undeclared identifier is reported only once for each function it appears in

vim +9485 kernel/bpf/verifier.c

  9467	
  9468	static int prepare_bpf_trampoline(struct bpf_verifier_env *env)
  9469	{
  9470		struct bpf_prog *prog = env->prog;
  9471		/* flags to attach at fentry */
  9472		u32 flags = BPF_TRAMP_F_RESTORE_REGS;
  9473		void *tramp;
  9474	
  9475		if (!prog->aux->needs_trampoline)
  9476			return 0;
  9477	
  9478		if (prog->expected_attach_type == BPF_TRACE_FEXIT)
  9479			/* flags to attach at fentry with kretprobe-like behavior */
  9480			flags = BPF_TRAMP_F_CALL_ORIG | BPF_TRAMP_F_SKIP_FRAME;
  9481		tramp = arch_prepare_bpf_trampoline(&prog->aux->attach_func_model,
  9482						    flags,
  9483						    __bpf_prog_run_from_trampoline,
  9484						    (long)prog,
> 9485						    prog->aux->attach_func_addr + MCOUNT_INSN_SIZE);
  9486		if (IS_ERR(tramp))
  9487			return PTR_ERR(tramp);
  9488		prog->aux->trampoline = tramp;
  9489		return 0;
  9490	}
  9491	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

                 reply	other threads:[~2019-10-31  3:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201910311139.e6PLPOcc%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.