All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, "Pan, Kris" <kris.pan@intel.com>
Subject: [intel-lts:4.19/android_s 4060/30000] security/security.c:455:5: warning: no previous prototype for 'lsm_key_alloc'
Date: Thu, 15 Jun 2023 23:06:13 +0800	[thread overview]
Message-ID: <202306152333.cP9BSFAP-lkp@intel.com> (raw)

Hi Casey,

FYI, the error/warning still remains.

tree:   https://github.com/intel/linux-intel-lts.git 4.19/android_s
head:   84b0def7f5485c67cb173427c2009a55c6303842
commit: 1d4be734af45c0b49e13f8377be93c2f5cb01a6b [4060/30000] LSM: Infrastructure management of the key security blob
config: i386-randconfig-r021-20230615 (https://download.01.org/0day-ci/archive/20230615/202306152333.cP9BSFAP-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build):
        # https://github.com/intel/linux-intel-lts/commit/1d4be734af45c0b49e13f8377be93c2f5cb01a6b
        git remote add intel-lts https://github.com/intel/linux-intel-lts.git
        git fetch --no-tags intel-lts 4.19/android_s
        git checkout 1d4be734af45c0b49e13f8377be93c2f5cb01a6b
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=i386 olddefconfig
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash

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/202306152333.cP9BSFAP-lkp@intel.com/

All warnings (new ones prefixed by >>):

   security/security.c:332:5: warning: no previous prototype for 'lsm_file_alloc' [-Wmissing-prototypes]
     332 | int lsm_file_alloc(struct file *file)
         |     ^~~~~~~~~~~~~~
   security/security.c:353:5: warning: no previous prototype for 'lsm_task_alloc' [-Wmissing-prototypes]
     353 | int lsm_task_alloc(struct task_struct *task)
         |     ^~~~~~~~~~~~~~
   security/security.c:433:5: warning: no previous prototype for 'lsm_ipc_alloc' [-Wmissing-prototypes]
     433 | int lsm_ipc_alloc(struct kern_ipc_perm *kip)
         |     ^~~~~~~~~~~~~
>> security/security.c:455:5: warning: no previous prototype for 'lsm_key_alloc' [-Wmissing-prototypes]
     455 | int lsm_key_alloc(struct key *key)
         |     ^~~~~~~~~~~~~
   security/security.c:477:5: warning: no previous prototype for 'lsm_msg_msg_alloc' [-Wmissing-prototypes]
     477 | int lsm_msg_msg_alloc(struct msg_msg *mp)
         |     ^~~~~~~~~~~~~~~~~
   security/security.c:499:5: warning: no previous prototype for 'lsm_sock_alloc' [-Wmissing-prototypes]
     499 | int lsm_sock_alloc(struct sock *sock, gfp_t priority)
         |     ^~~~~~~~~~~~~~
   security/security.c:520:5: warning: no previous prototype for 'lsm_superblock_alloc' [-Wmissing-prototypes]
     520 | int lsm_superblock_alloc(struct super_block *sb)
         |     ^~~~~~~~~~~~~~~~~~~~


vim +/lsm_key_alloc +455 security/security.c

   445	
   446	#ifdef CONFIG_KEYS
   447	/**
   448	 * lsm_key_alloc - allocate a composite key blob
   449	 * @key: the key that needs a blob
   450	 *
   451	 * Allocate the key blob for all the modules
   452	 *
   453	 * Returns 0, or -ENOMEM if memory can't be allocated.
   454	 */
 > 455	int lsm_key_alloc(struct key *key)
   456	{
   457		if (blob_sizes.lbs_key == 0) {
   458			key->security = NULL;
   459			return 0;
   460		}
   461	
   462		key->security = kzalloc(blob_sizes.lbs_key, GFP_KERNEL);
   463		if (key->security == NULL)
   464			return -ENOMEM;
   465		return 0;
   466	}
   467	#endif /* CONFIG_KEYS */
   468	

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

                 reply	other threads:[~2023-06-15 15:26 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=202306152333.cP9BSFAP-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kris.pan@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.