From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@suse.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [hare-nvme:dhchap-keyring.v3 4/8] ld.lld: error: undefined symbol: nvme_auth_extract_key
Date: Sat, 21 Mar 2026 04:05:30 +0800 [thread overview]
Message-ID: <202603210330.k0wPRtgU-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/nvme.git dhchap-keyring.v3
head: 7ffdb5e32339cf1e1ba50b8caefaca6dbab4d882
commit: 56494fb17cb0605fe7b0f49407538715a2fea547 [4/8] nvme: parse dhchap keys during option parsing
config: i386-randconfig-007-20260320 (https://download.01.org/0day-ci/archive/20260321/202603210330.k0wPRtgU-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260321/202603210330.k0wPRtgU-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202603210330.k0wPRtgU-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: nvme_auth_extract_key
>>> referenced by fabrics.c:1097 (drivers/nvme/host/fabrics.c:1097)
>>> drivers/nvme/host/fabrics.o:(nvmf_dev_write) in archive vmlinux.a
>>> referenced by fabrics.c:1112 (drivers/nvme/host/fabrics.c:1112)
>>> drivers/nvme/host/fabrics.o:(nvmf_dev_write) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-20 20:06 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=202603210330.k0wPRtgU-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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