From: kernel test robot <lkp@intel.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Nathan Chancellor <nathan@kernel.org>,
Kees Cook <kees@kernel.org>, Nicolas Schier <n.schier@fritz.com>
Subject: [kbuild:kbuild-next-speedups 10/21] llvm-objcopy: error: 'vmlinux.unstripped': section '.modinfo' not found
Date: Mon, 28 Sep 2026 11:48:55 +0800 [thread overview]
Message-ID: <202609281114.YdStyybd-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-next-speedups
head: a98db7418797bc27bef53c861b97ac748f598414
commit: 5fe4dd59664105a9ea1a9468aa7391806b80364a [10/21] kbuild: do not allocate .modinfo in vmlinux
config: arm-randconfig-1002-20260928 (https://download.01.org/0day-ci/archive/20260928/202609281114.YdStyybd-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 5f609f950d2e80addf5566623013db68394334db)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260928/202609281114.YdStyybd-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/202609281114.YdStyybd-lkp@intel.com/
Note: the kbuild/kbuild-next-speedups HEAD a98db7418797bc27bef53c861b97ac748f598414 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> llvm-objcopy: error: 'vmlinux.unstripped': section '.modinfo' not found
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-28 3:49 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=202609281114.YdStyybd-lkp@intel.com \
--to=lkp@intel.com \
--cc=kees@kernel.org \
--cc=ljs@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=n.schier@fritz.com \
--cc=nathan@kernel.org \
--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.