From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [ardb:x86-efi-zboot 11/16] ld.lld: error: undefined hidden symbol: pv_ops
Date: Mon, 27 Jan 2025 15:17:23 +0800 [thread overview]
Message-ID: <202501271543.iaTbLKPJ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git x86-efi-zboot
head: 10a91ad0b8cdac55ad6dd0392df03e80942eef51
commit: 22bf9d7e4b29ece8d06e0caef03289622ec443db [11/16] x86/efistub: Move EFI stub specific code into stub sources
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20250127/202501271543.iaTbLKPJ-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250127/202501271543.iaTbLKPJ-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/202501271543.iaTbLKPJ-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined hidden symbol: pv_ops
>>> referenced by x86-stub.c
>>> x86-stub.stub.o:(arch_accept_memory) in archive drivers/firmware/efi/libstub/lib.a
>>> referenced by x86-stub.c
>>> x86-stub.stub.o:(arch_accept_memory) in archive drivers/firmware/efi/libstub/lib.a
--
>> ld.lld: error: undefined symbol: BUG_func
>>> referenced by x86-stub.c
>>> x86-stub.stub.o:(.altinstr_replacement+0x1) in archive drivers/firmware/efi/libstub/lib.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-27 7:18 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=202501271543.iaTbLKPJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--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