All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev, Paul Moore <paul@paul-moore.com>
Subject: [linuxsecuritymodule:next 7/11] security/hornet/hornet_lsm.c:44:23: sparse: sparse: symbol 'hornet_blob_sizes' was not declared. Should it be static?
Date: Thu, 14 May 2026 15:31:40 +0800	[thread overview]
Message-ID: <202605141546.35eja3ay-lkp@intel.com> (raw)

tree:   https://github.com/LinuxSecurityModule/kernel next
head:   7cd0da3c29d22e2a8dcbc995b12199bc3d2704a8
commit: c62310df81899f7e14d632271aba08d0a55e2318 [7/11] lsm: introduce the Hornet LSM
config: hexagon-randconfig-r134-20260514 (https://download.01.org/0day-ci/archive/20260514/202605141546.35eja3ay-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260514/202605141546.35eja3ay-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/202605141546.35eja3ay-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> security/hornet/hornet_lsm.c:44:23: sparse: sparse: symbol 'hornet_blob_sizes' was not declared. Should it be static?

vim +/hornet_blob_sizes +44 security/hornet/hornet_lsm.c

    43	
  > 44	struct lsm_blob_sizes hornet_blob_sizes __ro_after_init = {
    45		.lbs_bpf_prog = sizeof(struct hornet_prog_security_struct),
    46	};
    47	

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

                 reply	other threads:[~2026-05-14  7:31 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=202605141546.35eja3ay-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bboscaccy@linux.microsoft.com \
    --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 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.