public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [RFC 01/20] ima: Add IMA namespace support
Date: Wed, 1 Dec 2021 05:53:09 +0800	[thread overview]
Message-ID: <202112010524.0QqCKzjC-lkp@intel.com> (raw)
In-Reply-To: <20211130160654.1418231-2-stefanb@linux.ibm.com>

Hi Stefan,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on zohar-integrity/next-integrity]
[also build test WARNING on pcmoore-selinux/next linus/master v5.16-rc3 next-20211130]
[cannot apply to jmorris-security/next-testing]
[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]

url:    https://github.com/0day-ci/linux/commits/Stefan-Berger/ima-Namespace-IMA-with-audit-support-in-IMA-ns/20211201-001242
base:   https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity
config: arm-randconfig-r014-20211128 (https://download.01.org/0day-ci/archive/20211201/202112010524.0QqCKzjC-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 25eb7fa01d7ebbe67648ea03841cda55b4239ab2)
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 arm cross compiling tool for clang build
        # apt-get install binutils-arm-linux-gnueabi
        # https://github.com/0day-ci/linux/commit/38ca49ebd9eb92c7975ca8d04ed1a4aa4959e96a
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Stefan-Berger/ima-Namespace-IMA-with-audit-support-in-IMA-ns/20211201-001242
        git checkout 38ca49ebd9eb92c7975ca8d04ed1a4aa4959e96a
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash security/integrity/ima/

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

All warnings (new ones prefixed by >>):

>> security/integrity/ima/ima_ns.c:77:12: warning: no previous prototype for function 'imans_cache_init' [-Wmissing-prototypes]
   int __init imans_cache_init(void)
              ^
   security/integrity/ima/ima_ns.c:77:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
   int __init imans_cache_init(void)
   ^
   static 
   1 warning generated.


vim +/imans_cache_init +77 security/integrity/ima/ima_ns.c

    76	
  > 77	int __init imans_cache_init(void)

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

       reply	other threads:[~2021-11-30 21:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211130160654.1418231-2-stefanb@linux.ibm.com>
2021-11-30 21:53 ` kernel test robot [this message]
2021-11-30 22:03 ` [RFC 01/20] ima: Add IMA namespace support kernel test robot

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=202112010524.0QqCKzjC-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=llvm@lists.linux.dev \
    --cc=stefanb@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