From: kernel test robot <lkp@intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Paul Moore <paul@paul-moore.com>
Subject: [linux-next:master 3278/3762] security/selinux/hooks.c:249:41: sparse: sparse: Using plain integer as NULL pointer
Date: Fri, 21 Jul 2023 03:18:54 +0800 [thread overview]
Message-ID: <202307210332.4AqFZfzI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c58c49dd89324b18a812762a2bfa5a0458e4f252
commit: dd51fcd42fd6bf37608f54303b974b47f73c1490 [3278/3762] selinux: introduce and use lsm_ad_net_init*() helpers
config: x86_64-randconfig-x063-20230720 (https://download.01.org/0day-ci/archive/20230721/202307210332.4AqFZfzI-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230721/202307210332.4AqFZfzI-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/202307210332.4AqFZfzI-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> security/selinux/hooks.c:249:41: sparse: sparse: Using plain integer as NULL pointer
security/selinux/hooks.c:5392:22: sparse: sparse: restricted __be16 degrades to integer
security/selinux/hooks.c:5393:22: sparse: sparse: restricted __be16 degrades to integer
vim +249 security/selinux/hooks.c
244
245 static void ad_net_init_from_iif(struct common_audit_data *ad,
246 struct lsm_network_audit *net,
247 int ifindex, u16 family)
248 {
> 249 __ad_net_init(ad, net, ifindex, 0, family);
250 }
251
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-20 19:21 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=202307210332.4AqFZfzI-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox