From: kernel test robot <lkp@intel.com>
To: Roberto Sassu <roberto.sassu@huawei.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [robertosassu:ima-evm-lsms-v6-devel-v4 22/26] security/integrity/evm/evm_main.c:1061:12: warning: no previous prototype for function 'init_evm_lsm'
Date: Tue, 21 Nov 2023 13:06:16 +0800 [thread overview]
Message-ID: <202311211244.2uqAiAnr-lkp@intel.com> (raw)
tree: https://github.com/robertosassu/linux ima-evm-lsms-v6-devel-v4
head: 58605e8f9256d446ad8fa46474f4a402a68715a5
commit: ab43d28d22d09d87c91646df14890fa542f9dc3d [22/26] evm: Move to LSM infrastructure
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20231121/202311211244.2uqAiAnr-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231121/202311211244.2uqAiAnr-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/202311211244.2uqAiAnr-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> security/integrity/evm/evm_main.c:1061:12: warning: no previous prototype for function 'init_evm_lsm' [-Wmissing-prototypes]
int __init init_evm_lsm(void)
^
security/integrity/evm/evm_main.c:1061:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int __init init_evm_lsm(void)
^
static
1 warning generated.
vim +/init_evm_lsm +1061 security/integrity/evm/evm_main.c
1054
1055 /*
1056 * Since with the LSM_ORDER_LAST there is no guarantee about the ordering
1057 * within the .lsm_info.init section, ensure that IMA hooks are before EVM
1058 * ones, by letting the 'integrity' LSM call init_evm_lsm() to initialize the
1059 * 'ima' and 'evm' LSMs in this sequence.
1060 */
> 1061 int __init init_evm_lsm(void)
1062 {
1063 security_add_hooks(evm_hooks, ARRAY_SIZE(evm_hooks), &evm_lsmid);
1064 return 0;
1065 }
1066
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-21 5:06 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=202311211244.2uqAiAnr-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=roberto.sassu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox