llvm.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
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 1/8] certs: Introduce ability to link to a system key
Date: Tue, 12 Mar 2024 16:55:46 +0800	[thread overview]
Message-ID: <202403121646.uVo3fDVV-lkp@intel.com> (raw)
In-Reply-To: <20240311161111.3268190-2-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-2-eric.snowberg%40oracle.com
patch subject: [PATCH RFC 1/8] certs: Introduce ability to link to a system key
config: arm-defconfig (https://download.01.org/0day-ci/archive/20240312/202403121646.uVo3fDVV-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240312/202403121646.uVo3fDVV-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/202403121646.uVo3fDVV-lkp@intel.com/

All errors (new ones prefixed by >>):

>> certs/system_keyring.c:447:29: error: use of undeclared identifier 'platform_trusted_keys'; did you mean 'set_platform_trusted_keys'?
           tkey = find_asymmetric_key(platform_trusted_keys, id, NULL, NULL, false);
                                      ^~~~~~~~~~~~~~~~~~~~~
                                      set_platform_trusted_keys
   include/keys/system_keyring.h:133:20: note: 'set_platform_trusted_keys' declared here
   static inline void set_platform_trusted_keys(struct key *keyring)
                      ^
   1 error generated.


vim +447 certs/system_keyring.c

   429	
   430	/**
   431	 * system_key_link - Link to a system key
   432	 * @keyring: The keyring to link into
   433	 * @id: The asymmetric key id to look for in the system keyring
   434	 */
   435	int system_key_link(struct key *keyring, struct asymmetric_key_id *id)
   436	{
   437		struct key *tkey;
   438	
   439	#ifdef CONFIG_SECONDARY_TRUSTED_KEYRING
   440		tkey = find_asymmetric_key(secondary_trusted_keys, id, NULL, NULL, false);
   441	#else
   442		tkey = find_asymmetric_key(builtin_trusted_keys, id, NULL, NULL, false);
   443	#endif
   444		if (!IS_ERR(tkey))
   445			goto found;
   446	
 > 447		tkey = find_asymmetric_key(platform_trusted_keys, id, NULL, NULL, false);

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

           reply	other threads:[~2024-03-12  8:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20240311161111.3268190-2-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=202403121646.uVo3fDVV-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).