public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Paul Moore <paul@paul-moore.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH v2 1/2] lsm: add backing_file LSM hooks
Date: Wed, 25 Mar 2026 03:31:44 +0800	[thread overview]
Message-ID: <202603250333.LaZDZOEq-lkp@intel.com> (raw)
In-Reply-To: <20260323042510.3331778-5-paul@paul-moore.com>

Hi Paul,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:

[auto build test WARNING on pcmoore-selinux/next]
[also build test WARNING on xiang-erofs/dev-test xiang-erofs/dev xiang-erofs/fixes linus/master v7.0-rc5 next-20260323]
[cannot apply to brauner-vfs/vfs.all]
[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/Paul-Moore/lsm-add-backing_file-LSM-hooks/20260324-111550
base:   https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git next
patch link:    https://lore.kernel.org/r/20260323042510.3331778-5-paul%40paul-moore.com
patch subject: [RFC PATCH v2 1/2] lsm: add backing_file LSM hooks
config: x86_64-allnoconfig (https://download.01.org/0day-ci/archive/20260325/202603250333.LaZDZOEq-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260325/202603250333.LaZDZOEq-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/202603250333.LaZDZOEq-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from kernel/sched/rq-offsets.c:5:
   In file included from kernel/sched/sched.h:64:
   In file included from include/linux/syscalls_api.h:1:
   In file included from include/linux/syscalls.h:95:
   In file included from include/trace/syscall.h:7:
   In file included from include/linux/trace_events.h:10:
   In file included from include/linux/perf_event.h:53:
>> include/linux/security.h:1149:5: warning: no previous prototype for function 'security_backing_file_alloc' [-Wmissing-prototypes]
    1149 | int security_backing_file_alloc(void **backing_file_blobp,
         |     ^
   include/linux/security.h:1149:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    1149 | int security_backing_file_alloc(void **backing_file_blobp,
         | ^
         | static 
>> include/linux/security.h:1155:6: warning: no previous prototype for function 'security_backing_file_free' [-Wmissing-prototypes]
    1155 | void security_backing_file_free(void **backing_file_blobp)
         |      ^
   include/linux/security.h:1155:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    1155 | void security_backing_file_free(void **backing_file_blobp)
         | ^
         | static 
   2 warnings generated.
--
   In file included from kernel/sched/rq-offsets.c:5:
   In file included from kernel/sched/sched.h:64:
   In file included from include/linux/syscalls_api.h:1:
   In file included from include/linux/syscalls.h:95:
   In file included from include/trace/syscall.h:7:
   In file included from include/linux/trace_events.h:10:
   In file included from include/linux/perf_event.h:53:
>> include/linux/security.h:1149:5: warning: no previous prototype for function 'security_backing_file_alloc' [-Wmissing-prototypes]
    1149 | int security_backing_file_alloc(void **backing_file_blobp,
         |     ^
   include/linux/security.h:1149:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    1149 | int security_backing_file_alloc(void **backing_file_blobp,
         | ^
         | static 
>> include/linux/security.h:1155:6: warning: no previous prototype for function 'security_backing_file_free' [-Wmissing-prototypes]
    1155 | void security_backing_file_free(void **backing_file_blobp)
         |      ^
   include/linux/security.h:1155:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
    1155 | void security_backing_file_free(void **backing_file_blobp)
         | ^
         | static 
   2 warnings generated.


vim +/security_backing_file_alloc +1149 include/linux/security.h

  1148	
> 1149	int security_backing_file_alloc(void **backing_file_blobp,
  1150					const struct file *user_file)
  1151	{
  1152		return 0;
  1153	}
  1154	
> 1155	void security_backing_file_free(void **backing_file_blobp)
  1156	{ }
  1157	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

           reply	other threads:[~2026-03-24 19:32 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260323042510.3331778-5-paul@paul-moore.com>]

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=202603250333.LaZDZOEq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paul@paul-moore.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