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.v2 63/67] tcp.c:undefined reference to `nvme_keyring_lookup_generated_key'
Date: Thu, 24 Feb 2022 14:48:09 +0800 [thread overview]
Message-ID: <202202241454.BxQTCDeq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git tls-upcall.v2
head: ac729ea3c52bda460616c71d5f5fc47b2e64da6d
commit: ab566bd55ff565627166db4334bb892488261c9c [63/67] nvme-tls: rename 'dhchap' to 'generated' key
config: openrisc-buildonly-randconfig-r005-20220223 (https://download.01.org/0day-ci/archive/20220224/202202241454.BxQTCDeq-lkp@intel.com/config)
compiler: or1k-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=ab566bd55ff565627166db4334bb892488261c9c
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.v2
git checkout ab566bd55ff565627166db4334bb892488261c9c
# 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=openrisc 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 >>):
or1k-linux-ld: drivers/nvme/host/core.o: in function `nvme_core_init':
core.c:(.init.text+0x1d8): undefined reference to `nvme_keyring_init'
core.c:(.init.text+0x1d8): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_init'
or1k-linux-ld: drivers/nvme/host/tcp.o: in function `nvme_tcp_start_tls':
tcp.c:(.text+0xd10): undefined reference to `tls_client_hello_user'
tcp.c:(.text+0xd10): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `tls_client_hello_user'
or1k-linux-ld: drivers/nvme/host/tcp.o: in function `nvme_tcp_lookup_psk.constprop.0':
>> tcp.c:(.text+0x2ed8): undefined reference to `nvme_keyring_lookup_generated_key'
tcp.c:(.text+0x2ed8): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_lookup_generated_key'
or1k-linux-ld: tcp.c:(.text+0x2efc): undefined reference to `nvme_keyring_lookup_tls'
tcp.c:(.text+0x2efc): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_lookup_tls'
or1k-linux-ld: tcp.c:(.text+0x2f28): undefined reference to `nvme_keyring_lookup_psk'
tcp.c:(.text+0x2f28): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_lookup_psk'
or1k-linux-ld: tcp.c:(.text+0x2f44): undefined reference to `nvme_keyring_insert_tls'
tcp.c:(.text+0x2f44): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_insert_tls'
>> or1k-linux-ld: tcp.c:(.text+0x2f6c): undefined reference to `nvme_keyring_lookup_generated_key'
tcp.c:(.text+0x2f6c): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_lookup_generated_key'
or1k-linux-ld: tcp.c:(.text+0x2f8c): undefined reference to `nvme_keyring_insert_tls'
tcp.c:(.text+0x2f8c): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_insert_tls'
or1k-linux-ld: tcp.c:(.text+0x2fb0): undefined reference to `nvme_keyring_lookup_tls'
tcp.c:(.text+0x2fb0): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_lookup_tls'
or1k-linux-ld: tcp.c:(.text+0x2fdc): undefined reference to `nvme_keyring_lookup_psk'
tcp.c:(.text+0x2fdc): relocation truncated to fit: R_OR1K_INSN_REL_26 against undefined symbol `nvme_keyring_lookup_psk'
or1k-linux-ld: tcp.c:(.text+0x2ff8): undefined reference to `nvme_keyring_insert_tls'
tcp.c:(.text+0x2ff8): additional relocation overflows omitted from the output
or1k-linux-ld: tcp.c:(.text+0x3054): undefined reference to `nvme_keyring_insert_tls'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-02-24 6:49 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=202202241454.BxQTCDeq-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
all inboxes | Powered by JetHome®