From: kernel test robot <lkp@intel.com>
To: Eric Snowberg <eric.snowberg@oracle.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC 2/8] clavis: Introduce a new system keyring called clavis
Date: Tue, 12 Mar 2024 18:49:16 +0800 [thread overview]
Message-ID: <202403121804.3aCRnfuH-lkp@intel.com> (raw)
In-Reply-To: <20240311161111.3268190-3-eric.snowberg@oracle.com>
Hi Eric,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on edc6670233a333ccfd1ec0548f068bd121d209c8]
url: https://github.com/intel-lab-lkp/linux/commits/Eric-Snowberg/certs-Introduce-ability-to-link-to-a-system-key/20240312-002925
base: edc6670233a333ccfd1ec0548f068bd121d209c8
patch link: https://lore.kernel.org/r/20240311161111.3268190-3-eric.snowberg%40oracle.com
patch subject: [PATCH RFC 2/8] clavis: Introduce a new system keyring called clavis
config: riscv-defconfig (https://download.01.org/0day-ci/archive/20240312/202403121804.3aCRnfuH-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 503c55e17037436dcd45ac69dea8967e67e3f5e8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240312/202403121804.3aCRnfuH-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/202403121804.3aCRnfuH-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: late_init_clavis_setup
>>> referenced by iint.c
>>> security/integrity/iint.o:(integrity_load_keys) in archive vmlinux.a
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-03-12 10:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240311161111.3268190-3-eric.snowberg@oracle.com>]
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=202403121804.3aCRnfuH-lkp@intel.com \
--to=lkp@intel.com \
--cc=eric.snowberg@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).