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:auth.v4 10/11] configfs.c:undefined reference to `nvme_auth_dhgroup_id'
Date: Mon, 19 Jul 2021 08:38:28 +0800 [thread overview]
Message-ID: <202107190826.GXczfruh-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3649 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git auth.v4
head: d22f44dbe36eb82041e9e28db6a767c55c8d790e
commit: 37535123b7f58ea4eecceb2bf236f12446672efd [10/11] nvmet-auth: implement support for augmented challenge
config: riscv-randconfig-c004-20210718 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 10.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/hare/scsi-devel.git/commit/?id=37535123b7f58ea4eecceb2bf236f12446672efd
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 auth.v4
git checkout 37535123b7f58ea4eecceb2bf236f12446672efd
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.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/target/configfs.o: in function `nvmet_host_dhchap_dhgroup_store':
>> configfs.c:(.text+0x28): undefined reference to `nvme_auth_dhgroup_id'
>> riscv64-linux-ld: configfs.c:(.text+0x60): undefined reference to `nvme_auth_dhgroup_kpp'
riscv64-linux-ld: drivers/nvme/target/configfs.o: in function `nvmet_host_dhchap_dhgroup_show':
>> configfs.c:(.text+0xa0): undefined reference to `nvme_auth_dhgroup_name'
riscv64-linux-ld: drivers/nvme/target/configfs.o: in function `nvmet_host_dhchap_hash_show':
configfs.c:(.text+0x5a0): undefined reference to `nvme_auth_hmac_name'
riscv64-linux-ld: drivers/nvme/target/configfs.o: in function `nvmet_host_dhchap_hash_store':
configfs.c:(.text+0x608): undefined reference to `nvme_auth_hmac_id'
riscv64-linux-ld: configfs.c:(.text+0x618): undefined reference to `nvme_auth_hmac_name'
riscv64-linux-ld: drivers/nvme/target/fabrics-cmd-auth.o: in function `.L36':
fabrics-cmd-auth.c:(.text+0xe0): undefined reference to `nvme_auth_hmac_id'
riscv64-linux-ld: drivers/nvme/target/auth.o: in function `nvmet_auth_augmented_challenge':
>> auth.c:(.text+0x8c): undefined reference to `nvme_auth_hmac_id'
>> riscv64-linux-ld: auth.c:(.text+0x98): undefined reference to `nvme_auth_digest_name'
riscv64-linux-ld: drivers/nvme/target/auth.o: in function `.L0 ':
auth.c:(.text+0x298): undefined reference to `nvme_auth_hmac_name'
riscv64-linux-ld: drivers/nvme/target/auth.o: in function `.L40':
>> auth.c:(.text+0x434): undefined reference to `nvme_auth_dhgroup_kpp'
>> riscv64-linux-ld: auth.c:(.text+0x46c): undefined reference to `nvme_auth_dhgroup_pubkey_size'
riscv64-linux-ld: drivers/nvme/target/auth.o: in function `.L61':
auth.c:(.text+0x538): undefined reference to `nvme_auth_hmac_name'
riscv64-linux-ld: auth.c:(.text+0x574): undefined reference to `nvme_auth_extract_secret'
riscv64-linux-ld: auth.c:(.text+0x590): undefined reference to `nvme_auth_hmac_name'
riscv64-linux-ld: drivers/nvme/target/auth.o: in function `nvmet_auth_ctrl_exponential':
>> auth.c:(.text+0xdc0): undefined reference to `nvme_auth_dhgroup_pubkey_size'
riscv64-linux-ld: drivers/nvme/target/auth.o: in function `nvmet_auth_ctrl_sesskey':
auth.c:(.text+0x1008): undefined reference to `nvme_auth_dhgroup_privkey_size'
---
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: 47103 bytes --]
reply other threads:[~2021-07-19 0:39 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=202107190826.GXczfruh-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