From: kbuild test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: [tip:efi/core 62/64] undefined reference to `__efi64_thunk'
Date: Wed, 22 Jan 2020 14:46:14 +0800 [thread overview]
Message-ID: <202001221409.MI9Nbbe4%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi/core
head: 615bf8d9a96b3695eb6bb9b35c2279f5a17fd8c3
commit: 3cc028619e284188cdde652631e1c3c5a83692b9 [62/64] efi/x86: avoid KASAN false positives when accessing the 1: 1 mapping
config: x86_64-randconfig-h001-20200121 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
git checkout 3cc028619e284188cdde652631e1c3c5a83692b9
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: arch/x86/platform/efi/efi_64.o: in function `efi_set_virtual_address_map':
>> (.init.text+0xda2): undefined reference to `__efi64_thunk'
>> ld: (.init.text+0xe12): undefined reference to `efi_uv1_memmap_phys_prolog'
>> ld: (.init.text+0xec0): undefined reference to `efi_uv1_memmap_phys_epilog'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40731 bytes --]
reply other threads:[~2020-01-22 6:46 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=202001221409.MI9Nbbe4%lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@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®