From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, Jinjie Ruan <ruanjinjie@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 691/14344] ld.lld: error: undefined symbol: arch_elf_adjust_prot
Date: Thu, 10 Oct 2024 18:59:53 +0800 [thread overview]
Message-ID: <202410101809.HFdpybos-lkp@intel.com> (raw)
Hi Yury,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: f7c1291d7c3f15bc448cd93e29fa539386fe85fe
commit: 7de3ab4c3dd938fae3626a6344830b018eb7ba4f [691/14344] arm64: introduce binfmt_elf32.c
config: arm64-randconfig-004-20241010 (https://download.01.org/0day-ci/archive/20241010/202410101809.HFdpybos-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 70e0a7e7e6a8541bcc46908c592eed561850e416)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241010/202410101809.HFdpybos-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/202410101809.HFdpybos-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: arch_elf_adjust_prot
>>> referenced by binfmt_elf.c:583 (arch/arm64/kernel/../../../fs/binfmt_elf.c:583)
>>> arch/arm64/kernel/binfmt_elf32.o:(load_elf_binary) in archive vmlinux.a
>>> referenced by binfmt_elf.c:583 (arch/arm64/kernel/../../../fs/binfmt_elf.c:583)
>>> arch/arm64/kernel/binfmt_elf32.o:(load_elf_interp) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-10 11:00 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=202410101809.HFdpybos-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ruanjinjie@huawei.com \
/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.