linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Alexei Starovoitov <ast@kernel.org>
Subject: [linux-next:master 1891/4016] riscv64-linux-ld: bpf_jit_core.c:undefined reference to `bpf_jit_enable'
Date: Thu, 20 May 2021 21:23:06 +0800	[thread overview]
Message-ID: <202105202104.iGoWgy8R-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   7a42b92b6d30c3f09629c7d5ada9e3de2aba01af
commit: b24abcff918a5cbf44b0c982bd3477a93e8e4911 [1891/4016] bpf, kconfig: Add consolidated menu entry for bpf with core options
config: riscv-randconfig-c004-20210520 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.0
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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b24abcff918a5cbf44b0c982bd3477a93e8e4911
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout b24abcff918a5cbf44b0c982bd3477a93e8e4911
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv 

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

Note: the linux-next/master HEAD 7a42b92b6d30c3f09629c7d5ada9e3de2aba01af builds fine.
      It may have been fixed somewhere.

All errors (new ones prefixed by >>):

   riscv64-linux-ld: arch/riscv/net/bpf_jit_core.o: in function `bpf_int_jit_compile':
>> bpf_jit_core.c:(.text+0x13a): undefined reference to `bpf_jit_blind_constants'
>> riscv64-linux-ld: bpf_jit_core.c:(.text+0x190): undefined reference to `bpf_jit_enable'
>> riscv64-linux-ld: bpf_jit_core.c:(.text+0x1e6): undefined reference to `bpf_jit_prog_release_other'
>> riscv64-linux-ld: bpf_jit_core.c:(.text+0x20a): undefined reference to `bpf_jit_binary_free'
>> riscv64-linux-ld: bpf_jit_core.c:(.text+0x2e6): undefined reference to `bpf_jit_binary_alloc'
   riscv64-linux-ld: arch/riscv/net/bpf_jit_comp64.o: in function `.L750':
>> bpf_jit_comp64.c:(.text+0x234c): undefined reference to `bpf_jit_get_func_addr'
   riscv64-linux-ld: kernel/extable.o: in function `.L0 ':
   extable.c:(.text+0x9c): undefined reference to `search_bpf_extables'
   riscv64-linux-ld: kernel/extable.o: in function `.L31':
   extable.c:(.text+0x208): undefined reference to `is_bpf_text_address'
   riscv64-linux-ld: kernel/kallsyms.o: in function `.L69':
   kallsyms.c:(.text+0x2e6): undefined reference to `__bpf_address_lookup'
   riscv64-linux-ld: kernel/kallsyms.o: in function `.L75':
   kallsyms.c:(.text+0x3d2): undefined reference to `__bpf_address_lookup'

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for LOCKDEP
   Depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT && (FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86)
   Selected by
   - PROVE_LOCKING && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
   - LOCK_STAT && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
   - DEBUG_LOCK_ALLOC && DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT

---
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: 21311 bytes --]

             reply	other threads:[~2021-05-20 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 13:23 kernel test robot [this message]
2021-05-20 21:04 ` Daniel Borkmann

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=202105202104.iGoWgy8R-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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