linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Coiby Xu <coxu@redhat.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>
Subject: [zohar-integrity:next-integrity-testing 4/6] security/integrity/ima/ima_efi.c:72:4: error: call to undeclared function 'set_kexec_sig_enforced'; ISO C99 and later do not support implicit function declarations
Date: Tue, 12 Jul 2022 23:20:04 +0800	[thread overview]
Message-ID: <202207122330.FCO2VFHx-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity-testing
head:   e56ed3d80c69511a4af9db0b76e54e6763a63ef1
commit: 7be7b6c5b42fe7661a3abfaecf0910255781771f [4/6] ima: force signature verification when CONFIG_KEXEC_SIG is configured
config: arm64-randconfig-r032-20220712 (https://download.01.org/0day-ci/archive/20220712/202207122330.FCO2VFHx-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project badda4ac3c489a8c8cccdad1f74b9308c350a9e0)
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # install arm64 cross compiling tool for clang build
        # apt-get install binutils-aarch64-linux-gnu
        # https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git/commit/?id=7be7b6c5b42fe7661a3abfaecf0910255781771f
        git remote add zohar-integrity https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git
        git fetch --no-tags zohar-integrity next-integrity-testing
        git checkout 7be7b6c5b42fe7661a3abfaecf0910255781771f
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash security/integrity/ima/

If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

>> security/integrity/ima/ima_efi.c:72:4: error: call to undeclared function 'set_kexec_sig_enforced'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
                           set_kexec_sig_enforced();
                           ^
   security/integrity/ima/ima_efi.c:72:4: note: did you mean 'set_module_sig_enforced'?
   include/linux/module.h:809:20: note: 'set_module_sig_enforced' declared here
   static inline void set_module_sig_enforced(void)
                      ^
   1 error generated.


vim +/set_kexec_sig_enforced +72 security/integrity/ima/ima_efi.c

    65	
    66	const char * const *arch_get_ima_policy(void)
    67	{
    68		if (IS_ENABLED(CONFIG_IMA_ARCH_POLICY) && arch_ima_get_secureboot()) {
    69			if (IS_ENABLED(CONFIG_MODULE_SIG))
    70				set_module_sig_enforced();
    71			if (IS_ENABLED(CONFIG_KEXEC_SIG))
  > 72				set_kexec_sig_enforced();

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-07-12 15:22 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=202207122330.FCO2VFHx-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=coxu@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=zohar@linux.ibm.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 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).