public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@suse.de>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [hare-scsi-devel:tls-upcall.v4 140/156] tcp.c:undefined reference to `nvme_keyring_lookup_generated_key'
Date: Sun, 13 Mar 2022 21:33:14 +0800	[thread overview]
Message-ID: <202203132117.2HedNSTG-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git tls-upcall.v4
head:   d2416ecdb6b03fc2e4aa40b20cdf919322713224
commit: 2025db31c639eb71ba4cd675cb846a14a48cd932 [140/156] nvme-tcp: derive retained keys for TLS
config: riscv-randconfig-m031-20220313 (https://download.01.org/0day-ci/archive/20220313/202203132117.2HedNSTG-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 11.2.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/hare/scsi-devel.git/commit/?id=2025db31c639eb71ba4cd675cb846a14a48cd932
        git remote add hare-scsi-devel https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git
        git fetch --no-tags hare-scsi-devel tls-upcall.v4
        git checkout 2025db31c639eb71ba4cd675cb846a14a48cd932
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=riscv SHELL=/bin/bash

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 >>):

   riscv64-linux-ld: drivers/nvme/host/core.o: in function `nvme_core_exit':
   core.c:(.exit.text+0x8): undefined reference to `nvme_keyring_exit'
   riscv64-linux-ld: drivers/nvme/host/core.o: in function `.L0 ':
   core.c:(.init.text+0x17c): undefined reference to `nvme_keyring_init'
   riscv64-linux-ld: drivers/nvme/host/tcp.o: in function `.L646':
>> tcp.c:(.text+0x3188): undefined reference to `nvme_keyring_lookup_generated_key'
   riscv64-linux-ld: drivers/nvme/host/tcp.o: in function `.L649':
   tcp.c:(.text+0x31c2): undefined reference to `nvme_keyring_lookup_tls'
   riscv64-linux-ld: drivers/nvme/host/tcp.o: in function `nvme_tcp_timeout':
   tcp.c:(.text+0x3200): undefined reference to `nvme_keyring_lookup_generated_key'
>> riscv64-linux-ld: tcp.c:(.text+0x3238): undefined reference to `nvme_keyring_lookup_tls'
   riscv64-linux-ld: tcp.c:(.text+0x3290): undefined reference to `nvme_keyring_insert_tls'
   riscv64-linux-ld: tcp.c:(.text+0x32d2): undefined reference to `nvme_keyring_insert_tls'
   riscv64-linux-ld: drivers/nvme/host/tcp.o: in function `.L665':
>> tcp.c:(.text+0x3310): undefined reference to `nvme_keyring_lookup_retained_key'
   riscv64-linux-ld: drivers/nvme/host/tcp.o: in function `nvme_tcp_handle_r2t':
>> tcp.c:(.text+0x3344): undefined reference to `nvme_keyring_insert_tls'
   riscv64-linux-ld: tcp.c:(.text+0x3382): undefined reference to `nvme_keyring_lookup_retained_key'
   riscv64-linux-ld: tcp.c:(.text+0x33b6): undefined reference to `nvme_keyring_insert_tls'

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

                 reply	other threads:[~2022-03-13 13:34 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=202203132117.2HedNSTG-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hare@suse.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.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