From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jsarha:topic/chromeos-4.19-s0ix 7414/9999] security/container/process.c:367:5: warning: no previous prototype for 'csm_set_contid'
Date: Thu, 18 Jan 2024 04:43:54 +0800 [thread overview]
Message-ID: <202401180411.aPUEx6IX-lkp@intel.com> (raw)
tree: https://github.com/jsarha/linux topic/chromeos-4.19-s0ix
head: 430bdaa0a8c38697780f45a148964d71951df11f
commit: 92dff21f44ad18e109b6e086a29141fe474b3782 [7414/9999] CHROMIUM: security: Container Monitoring LSM
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20240118/202401180411.aPUEx6IX-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240118/202401180411.aPUEx6IX-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/202401180411.aPUEx6IX-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> security/container/process.c:367:5: warning: no previous prototype for 'csm_set_contid' [-Wmissing-prototypes]
367 | u64 csm_set_contid(struct task_struct *task)
| ^~~~~~~~~~~~~~
vim +/csm_set_contid +367 security/container/process.c
366
> 367 u64 csm_set_contid(struct task_struct *task)
368 {
369 u64 cid;
370
371 /* TODO: Report error to the backend */
372 if (WARN_ON(!task->audit))
373 return AUDIT_CID_UNSET;
374
375 cid = atomic_inc_return(&contid);
376 task->audit->contid = cid;
377 return cid;
378 }
379
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-17 20:44 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=202401180411.aPUEx6IX-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.