From: kernel test robot <lkp@intel.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: oe-kbuild-all@lists.linux.dev, Paul Moore <paul@paul-moore.com>,
Kees Cook <keescook@chromium.org>,
Serge Hallyn <serge@hallyn.com>, Mickael Salaun <mic@digikod.net>,
John Johansen <john.johansen@canonical.com>
Subject: [robertosassu:dev-staging 1/18] security/selinux/hooks.c:6954:21: sparse: sparse: symbol 'selinux_lsmid' was not declared. Should it be static?
Date: Fri, 10 Nov 2023 03:30:36 +0800 [thread overview]
Message-ID: <202311100355.eeC5cmYC-lkp@intel.com> (raw)
tree: https://github.com/robertosassu/linux dev-staging
head: ba7ce019d3e965aeb0d76d19d3f038b350b28bb2
commit: f347278284b81a0c1b1f46a0cbf1fe6a32493635 [1/18] LSM: Identify modules by more than name
config: x86_64-randconfig-123-20231109 (https://download.01.org/0day-ci/archive/20231110/202311100355.eeC5cmYC-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231110/202311100355.eeC5cmYC-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/202311100355.eeC5cmYC-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
security/selinux/hooks.c:5389:22: sparse: sparse: restricted __be16 degrades to integer
security/selinux/hooks.c:5390:22: sparse: sparse: restricted __be16 degrades to integer
>> security/selinux/hooks.c:6954:21: sparse: sparse: symbol 'selinux_lsmid' was not declared. Should it be static?
vim +/selinux_lsmid +6954 security/selinux/hooks.c
6953
> 6954 const struct lsm_id selinux_lsmid = {
6955 .name = "selinux",
6956 .id = LSM_ID_SELINUX,
6957 };
6958
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-09 19: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=202311100355.eeC5cmYC-lkp@intel.com \
--to=lkp@intel.com \
--cc=casey@schaufler-ca.com \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=mic@digikod.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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.