From: kernel test robot <lkp@intel.com>
To: John Johansen <john.johansen@canonical.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Georgia Garcia <georgia.garcia@canonical.com>
Subject: security/apparmor/lsm.c:1893:15: sparse: sparse: symbol 'nulldfa' was not declared. Should it be static?
Date: Thu, 9 Nov 2023 20:17:49 +0800 [thread overview]
Message-ID: <202311092038.lqfYnvmf-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 6bc986ab839c844e78a2333a02e55f02c9e57935
commit: 98b824ff8984fd523fc264fbb13208098ab09da3 apparmor: refcount the pdb
date: 3 weeks ago
config: i386-randconfig-062-20231104 (https://download.01.org/0day-ci/archive/20231109/202311092038.lqfYnvmf-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231109/202311092038.lqfYnvmf-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/202311092038.lqfYnvmf-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> security/apparmor/lsm.c:1893:15: sparse: sparse: symbol 'nulldfa' was not declared. Should it be static?
vim +/nulldfa +1893 security/apparmor/lsm.c
1889
1890 static char nulldfa_src[] = {
1891 #include "nulldfa.in"
1892 };
> 1893 struct aa_dfa *nulldfa;
1894
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-09 12:18 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=202311092038.lqfYnvmf-lkp@intel.com \
--to=lkp@intel.com \
--cc=georgia.garcia@canonical.com \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®