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 4/4] fuse_test.c:1400:9: warning: argument 1 null where non-null expected
Date: Thu, 30 Jul 2026 12:58:48 +0800 [thread overview]
Message-ID: <amraCH9A5ow4UmnI@rli9-mobl> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18
head: 5e9654c516d84286a1589d22470d9c4c04ed8507
commit: be926e6761d28d105ba672242e81e911e0d7e5e0 [4/4] ANDROID: fuse-bpf: fuse-bpf v1.3
config: arm64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260730/202607300651.2HBiyC2w-lkp@intel.com/config)
compiler: aarch64-linux-gnu-gcc (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260730/202607300651.2HBiyC2w-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/r/202607300651.2HBiyC2w-lkp@intel.com/
All warnings (new ones prefixed by >>):
fuse_test.c: In function 'readdir_perms_test':
>> fuse_test.c:1400:9: warning: argument 1 null where non-null expected [-Wnonnull]
1400 | closedir(dir);
| ^~~~~~~~~~~~~
In file included from test_fuse.h:13,
from fuse_test.c:7:
/usr/aarch64-linux-gnu/include/dirent.h:134:12: note: in a call to function 'closedir' declared 'nonnull'
134 | extern int closedir (DIR *__dirp) __nonnull ((1));
| ^~~~~~~~
fuse_test.c: In function 'inotify_test':
>> fuse_test.c:1455:9: warning: 'dir.s' may be used uninitialized [-Wmaybe-uninitialized]
1455 | free(dir.s);
| ^~~~~~~~~~~
fuse_test.c:1429:18: note: 'dir.s' was declared here
1429 | struct s dir;
| ^~~
In file included from test_fuse.h:11:
fuse_test.c: In function 'bpf_test_revalidate_handle_backing_fd':
>> fuse_test.c:1889:27: warning: 'read' writing 11 bytes into a region of size 9 overflows the destination [-Wstringop-overflow=]
1889 | TESTEQUAL(read(dst_content_fd, content_buffer, strlen(content)),
test_framework.h:137:56: note: in definition of macro '_CALL_TO'
137 | (_type) (long long) (a), \
| ^
test_framework.h:153:25: note: in expansion of macro 'TESTOPERATOR'
153 | #define TESTEQUAL(a, b) TESTOPERATOR(a, b, _eq)
| ^~~~~~~~~~~~
fuse_test.c:1889:17: note: in expansion of macro 'TESTEQUAL'
1889 | TESTEQUAL(read(dst_content_fd, content_buffer, strlen(content)),
| ^~~~~~~~~
fuse_test.c:1874:22: note: destination object 'content_buffer' of size 9
1874 | char content_buffer[9] = {0};
| ^~~~~~~~~~~~~~
In file included from ../../kselftest.h:55,
from test_framework.h:26:
/usr/aarch64-linux-gnu/include/unistd.h:371:16: note: in a call to function 'read' declared with attribute 'access (write_only, 2, 3)'
371 | extern ssize_t read (int __fd, void *__buf, size_t __nbytes) __wur
| ^~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-07-30 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 4:58 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-30 4:09 [android-common:android17-6.18 4/4] fuse_test.c:1400:9: warning: argument 1 null where non-null expected kernel test robot
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=amraCH9A5ow4UmnI@rli9-mobl \
--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.