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 linus/master v5.16-rc3]
[cannot apply to pcmoore-selinux/next next-20211130]
[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: i386-randconfig-s001-20211128 (https://download.01.org/0day-ci/archive/20211201/202112011144.GSq3J2Pi-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://github.com/0day-ci/linux/commit/659493ff54e52f8cb2023b00c5b86c13ed68ecdf
        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 659493ff54e52f8cb2023b00c5b86c13ed68ecdf
        # save the config file to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash

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


sparse warnings: (new ones prefixed by >>)
>> security/inode.c:243:15: sparse: sparse: symbol '_securityfs_create_symlink' was not declared. Should it be static?
>> security/inode.c:303:6: sparse: sparse: symbol '_securityfs_remove' was not declared. Should it be static?

Please review and possibly fold the followup patch.

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