From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb+git@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH PoC 08/11] x86/boot: Move startup code out of __head section
Date: Thu, 24 Apr 2025 23:12:46 +0800 [thread overview]
Message-ID: <202504242345.Zs1dvyW7-lkp@intel.com> (raw)
In-Reply-To: <20250423110948.1103030-21-ardb+git@google.com>
Hi Ard,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on 121c335b36e02d6aefb72501186e060474fdf33c]
url: https://github.com/intel-lab-lkp/linux/commits/Ard-Biesheuvel/x86-linkage-Add-SYM_PI_ALIAS-macro-helper-to-emit-symbol-aliases/20250423-191433
base: 121c335b36e02d6aefb72501186e060474fdf33c
patch link: https://lore.kernel.org/r/20250423110948.1103030-21-ardb%2Bgit%40google.com
patch subject: [RFC PATCH PoC 08/11] x86/boot: Move startup code out of __head section
config: x86_64-buildonly-randconfig-006-20250424 (https://download.01.org/0day-ci/archive/20250424/202504242345.Zs1dvyW7-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250424/202504242345.Zs1dvyW7-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/202504242345.Zs1dvyW7-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld: Unexpected GOT entries detected!
ld: vmlinux.o: in function `__pi_startup_64_load_idt':
>> (.text+0x1525c3): undefined reference to `__pi_memset'
>> ld: (.text+0x15262d): undefined reference to `__pi_memcpy'
ld: vmlinux.o: in function `__pi_startup_64_setup_gdt_idt':
>> (.init.text+0x42254): undefined reference to `__pi_latent_entropy'
ld: vmlinux.o: in function `__pi___startup_64':
(.init.text+0x422d5): undefined reference to `__pi_latent_entropy'
ld: .tmp_vmlinux1: hidden symbol `__pi_memcpy' isn't defined
ld: final link failed: bad value
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-24 15:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 11:09 [RFC PATCH PoC 00/11] x86: strict separation of startup code Ard Biesheuvel
2025-04-23 11:09 ` [RFC PATCH PoC 01/11] x86/linkage: Add SYM_PI_ALIAS() macro helper to emit symbol aliases Ard Biesheuvel
2025-04-24 18:05 ` Ingo Molnar
2025-04-24 18:17 ` Ard Biesheuvel
2025-04-24 18:23 ` Ingo Molnar
2025-04-23 11:09 ` [RFC PATCH PoC 02/11] x86/boot: Move early_setup_gdt() back into head64.c Ard Biesheuvel
2025-04-23 11:09 ` [RFC PATCH PoC 03/11] x86/boot: Disregard __supported_pte_mask in __startup_64() Ard Biesheuvel
2025-04-23 11:09 ` [RFC PATCH PoC 04/11] x86/boot: Add a bunch of PI aliases Ard Biesheuvel
2025-04-23 11:09 ` [RFC PATCH PoC 05/11] HACK: provide __pti_set_user_pgtbl() to startup code Ard Biesheuvel
2025-04-23 11:09 ` [RFC PATCH PoC 06/11] x86/boot: Created a confined code area for " Ard Biesheuvel
2025-04-23 11:09 ` [RFC PATCH PoC 07/11] HACK: work around sev-startup.c being omitted for now Ard Biesheuvel
2025-04-23 11:09 ` [RFC PATCH PoC 08/11] x86/boot: Move startup code out of __head section Ard Biesheuvel
2025-04-24 15:12 ` kernel test robot [this message]
2025-04-23 11:09 ` [RFC PATCH PoC 09/11] x86/boot: Disallow absolute symbol references in startup code Ard Biesheuvel
2025-04-23 11:09 ` [RFC PATCH PoC 10/11] x86/boot: Revert "Reject absolute references in .head.text" Ard Biesheuvel
2025-04-23 11:10 ` [RFC PATCH PoC 11/11] x86/boot: Get rid of the .head.text section Ard Biesheuvel
2025-04-24 18:09 ` [RFC PATCH PoC 00/11] x86: strict separation of startup code Ingo Molnar
2025-04-24 18:16 ` Ard Biesheuvel
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=202504242345.Zs1dvyW7-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb+git@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.