From: kernel test robot <lkp@intel.com>
To: Nicolas Bouchinet <nicolas.bouchinet@clip-os.org>,
linux-integrity@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
philippe.trebuchet@ssi.gouv.fr, zohar@linux.ibm.com,
dmitry.kasatkin@gmail.com, paul@paul-moore.com,
jmorris@namei.org, serge@hallyn.com, casey@schaufler-ca.com,
davem@davemloft.net, lucien.xin@gmail.com, vgoyal@redhat.com,
omosnace@redhat.com, mortonm@chromium.org,
nicolas.bouchinet@ssi.gouv.fr, mic@digikod.net,
cgzones@googlemail.com, linux-security-module@vger.kernel.org,
kpsingh@kernel.org, revest@chromium.org, jackmanb@chromium.org,
bpf@vger.kernel.org, roberto.sassu@huaweicloud.com
Subject: Re: [PATCH v3] evm: Correct inode_init_security hooks behaviors
Date: Wed, 26 Oct 2022 09:51:33 +0800 [thread overview]
Message-ID: <202210260935.DdbmSp0n-lkp@intel.com> (raw)
In-Reply-To: <Y1fu4jofqLHVDprT@archlinux>
[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]
Hi Nicolas,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on zohar-integrity/next-integrity]
[also build test WARNING on linus/master v6.1-rc2 next-20221025]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Nicolas-Bouchinet/evm-Correct-inode_init_security-hooks-behaviors/20221025-221337
base: https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
patch link: https://lore.kernel.org/r/Y1fu4jofqLHVDprT%40archlinux
patch subject: [PATCH v3] evm: Correct inode_init_security hooks behaviors
config: hexagon-randconfig-r002-20221023 (attached as .config)
compiler: clang version 16.0.0 (https://github.com/llvm/llvm-project 791a7ae1ba3efd6bca96338e10ffde557ba83920)
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
# https://github.com/intel-lab-lkp/linux/commit/acbbdcb851ed7cd1894efad182f0325db04b9e5a
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Nicolas-Bouchinet/evm-Correct-inode_init_security-hooks-behaviors/20221025-221337
git checkout acbbdcb851ed7cd1894efad182f0325db04b9e5a
# 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=hexagon SHELL=/bin/bash security/integrity/evm/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> security/integrity/evm/evm_main.c:310:5: warning: no previous prototype for function 'evm_protected_xattr' [-Wmissing-prototypes]
int evm_protected_xattr(const char *req_xattr_name)
^
security/integrity/evm/evm_main.c:310:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int evm_protected_xattr(const char *req_xattr_name)
^
static
1 warning generated.
vim +/evm_protected_xattr +310 security/integrity/evm/evm_main.c
309
> 310 int evm_protected_xattr(const char *req_xattr_name)
311 {
312 return evm_protected_xattr_common(req_xattr_name, false);
313 }
314
--
0-DAY CI Kernel Test Service
https://01.org/lkp
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32258 bytes --]
prev parent reply other threads:[~2022-10-26 1:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 14:12 [PATCH v3] evm: Correct inode_init_security hooks behaviors Nicolas Bouchinet
2022-10-25 16:07 ` kernel test robot
2022-10-26 1:51 ` kernel test robot [this message]
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=202210260935.DdbmSp0n-lkp@intel.com \
--to=lkp@intel.com \
--cc=bpf@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=cgzones@googlemail.com \
--cc=davem@davemloft.net \
--cc=dmitry.kasatkin@gmail.com \
--cc=jackmanb@chromium.org \
--cc=jmorris@namei.org \
--cc=kpsingh@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lucien.xin@gmail.com \
--cc=mic@digikod.net \
--cc=mortonm@chromium.org \
--cc=nicolas.bouchinet@clip-os.org \
--cc=nicolas.bouchinet@ssi.gouv.fr \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=philippe.trebuchet@ssi.gouv.fr \
--cc=revest@chromium.org \
--cc=roberto.sassu@huaweicloud.com \
--cc=serge@hallyn.com \
--cc=vgoyal@redhat.com \
--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).