From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-2026-06 0/1] fs/fuse/fuse_bpf_backing.c:156:16: sparse: sparse: Using plain integer as NULL pointer
Date: Sun, 06 Sep 2026 01:59:34 +0800 [thread overview]
Message-ID: <202609060108.q8MKmXJY-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18-2026-06
head: de2fe859a26ac8b782d8d325668854871edb9f6d
commit: be926e6761d28d105ba672242e81e911e0d7e5e0 [0/1] ANDROID: fuse-bpf: fuse-bpf v1.3
config: i386-randconfig-061-20260904 (https://download.01.org/0day-ci/archive/20260906/202609060108.q8MKmXJY-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260906/202609060108.q8MKmXJY-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/202609060108.q8MKmXJY-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/fuse/fuse_bpf_backing.c:156:16: sparse: sparse: Using plain integer as NULL pointer
fs/fuse/fuse_bpf_backing.c:315:16: sparse: sparse: Using plain integer as NULL pointer
>> fs/fuse/fuse_bpf_backing.c:862:48: sparse: sparse: incorrect type in argument 4 (different base types) @@ expected restricted __kernel_rwf_t [usertype] flags @@ got int @@
fs/fuse/fuse_bpf_backing.c:862:48: sparse: expected restricted __kernel_rwf_t [usertype] flags
fs/fuse/fuse_bpf_backing.c:862:48: sparse: got int
fs/fuse/fuse_bpf_backing.c:949:59: sparse: sparse: incorrect type in argument 4 (different base types) @@ expected restricted __kernel_rwf_t [usertype] flags @@ got int @@
fs/fuse/fuse_bpf_backing.c:949:59: sparse: expected restricted __kernel_rwf_t [usertype] flags
fs/fuse/fuse_bpf_backing.c:949:59: sparse: got int
>> fs/fuse/fuse_bpf_backing.c:2142:18: sparse: sparse: Initializer entry defined twice
fs/fuse/fuse_bpf_backing.c:2143:18: sparse: also defined here
vim +156 fs/fuse/fuse_bpf_backing.c
145
146 void *fuse_open_finalize(struct fuse_bpf_args *fa,
147 struct inode *inode, struct file *file, bool isdir)
148 {
149 struct fuse_file *ff = file->private_data;
150 struct fuse_open_out *foo = fa->out_args[0].value;
151
152 if (ff) {
153 ff->fh = foo->fh;
154 ff->nodeid = get_fuse_inode(inode)->nodeid;
155 }
> 156 return 0;
157 }
158
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-05 17:59 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=202609060108.q8MKmXJY-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.