All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [mszeredi-fuse:for-next 24/52] fuse_mnt.c:46:49: error: parameter 6 ('flags') has incomplete type
Date: Sun, 18 Oct 2026 09:43:38 +0200	[thread overview]
Message-ID: <202610170047.9ZeFYsLO-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: fuse-devel@lists.sourceforge.net
TO: Luis Henriques <luis@igalia.com>
CC: Miklos Szeredi <mszeredi@redhat.com>
CC: Amir Goldstein <amir73il@gmail.com>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
head:   4dd8d396740168f5379f332ad2c165d7f0f91953
commit: 1ee5d3698ee66fa1cf2ed0b874caa8dcd59c6c7f [24/52] selftests/fuse: convert fusectl test to fuse3
:::::: branch date: 7 hours ago
:::::: commit date: 35 hours ago
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20261017/202610170047.9ZeFYsLO-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261017/202610170047.9ZeFYsLO-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/202610170047.9ZeFYsLO-lkp@intel.com/

Note: the mszeredi-fuse/for-next HEAD 4dd8d396740168f5379f332ad2c165d7f0f91953 builds fine.
      It only hurts bisectability.

All error/warnings (new ones prefixed by >>):

>> fuse_mnt.c:46:30: warning: 'enum fuse_readdir_flags' declared inside parameter list will not be visible outside of this definition or declaration
      46 |                         enum fuse_readdir_flags flags)
         |                              ^~~~~~~~~~~~~~~~~~
>> fuse_mnt.c:46:49: error: parameter 6 ('flags') has incomplete type
      46 |                         enum fuse_readdir_flags flags)
         |                         ~~~~~~~~~~~~~~~~~~~~~~~~^~~~~
   fuse_mnt.c: In function 'test_readdir':
>> fuse_mnt.c:51:35: error: 'FUSE_FILL_DIR_DEFAULTS' undeclared (first use in this function)
      51 |         filler(buf, ".", NULL, 0, FUSE_FILL_DIR_DEFAULTS);
         |                                   ^~~~~~~~~~~~~~~~~~~~~~
   fuse_mnt.c:51:35: note: each undeclared identifier is reported only once for each function it appears in
>> fuse_mnt.c:51:9: error: too many arguments to function 'filler'
      51 |         filler(buf, ".", NULL, 0, FUSE_FILL_DIR_DEFAULTS);
         |         ^~~~~~
   fuse_mnt.c:52:9: error: too many arguments to function 'filler'
      52 |         filler(buf, "..", NULL, 0, FUSE_FILL_DIR_DEFAULTS);
         |         ^~~~~~
   fuse_mnt.c:53:9: error: too many arguments to function 'filler'
      53 |         filler(buf, test_path + 1, NULL, 0, FUSE_FILL_DIR_DEFAULTS);
         |         ^~~~~~
   fuse_mnt.c: At top level:
>> fuse_mnt.c:138:20: error: initialization of 'int (*)(const char *, struct stat *)' from incompatible pointer type 'int (*)(const char *, struct stat *, struct fuse_file_info *)' [-Wincompatible-pointer-types]
     138 |         .getattr = test_getattr,
         |                    ^~~~~~~~~~~~
   fuse_mnt.c:138:20: note: (near initialization for 'memfd_ops.getattr')
>> fuse_mnt.c:143:21: error: initialization of 'int (*)(const char *, off_t)' {aka 'int (*)(const char *, long int)'} from incompatible pointer type 'int (*)(const char *, off_t,  struct fuse_file_info *)' {aka 'int (*)(const char *, long int,  struct fuse_file_info *)'} [-Wincompatible-pointer-types]
     143 |         .truncate = test_truncate,
         |                     ^~~~~~~~~~~~~
   fuse_mnt.c:143:21: note: (near initialization for 'memfd_ops.truncate')

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-10-18  7:52 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=202610170047.9ZeFYsLO-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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.