From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: mszeredi@redhat.com, Shuah Khan <shuah@kernel.org>
Cc: luis@igalia.com, amir73il@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
nandinih@linux.ibm.com
Subject: [BUG / BUILD FAILURE] selftests/fuse: build failure with libfuse < 3.17.0 (RHEL 10 / fuse3-3.16.2)
Date: Thu, 12 Nov 2026 17:57:20 +0530 [thread overview]
Message-ID: <bc84cb05-55fe-43e7-9a6e-e6bbf2f5a9ff@linux.ibm.com> (raw)
Hi Miklos, Luis,
IBM CI has reported a build failure, while building selftests/fuse, due
to missing definitions in libfuse3 headers.
Environment:
OS: RHEL 10 (ppc64le)
Kernel: upstream (linux-next / mainline)
libfuse package: fuse3-devel-3.16.2-5.el10.ppc64le (pkg-config
--modversion fuse3 -> 3.16.2)
Build Errors:
In fuse_acl_cache_test.c & fuse_symlink_cache_test.c:
fuse_acl_cache_test.c: In function ‘fs_init’:
fuse_acl_cache_test.c:105:17: error: implicit declaration of function
‘fuse_set_feature_flag’ [-Wimplicit-function-declaration]
105 | fuse_set_feature_flag(conn, FUSE_CAP_POSIX_ACL);
| ^~~~~~~~~~~~~~~~~~~~~
make: *** [../../lib.mk:226:
/home/upstreamci/linux/tools/testing/selftests/filesystems/fuse/fuse_acl_cache_test]
Error 1
In fuse_mnt.c:
fuse_mnt.c: In function ‘test_readdir’:
fuse_mnt.c:51:35: error: ‘FUSE_FILL_DIR_DEFAULTS’ undeclared (first use
in this function); did you mean ‘FUSE_FILL_DIR_PLUS’?
51 | filler(buf, ".", NULL, 0, FUSE_FILL_DIR_DEFAULTS);
| ^~~~~~~~~~~~~~~~~~~~~~
| FUSE_FILL_DIR_PLUS
make: *** [../../lib.mk:226:
/home/upstreamci/linux/tools/testing/selftests/filesystems/fuse/fuse_mnt]
Error 1
If you happen to fix this, please add below tag.
Reported-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Regards,
Venkat.
reply other threads:[~2026-11-12 12:27 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=bc84cb05-55fe-43e7-9a6e-e6bbf2f5a9ff@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luis@igalia.com \
--cc=mszeredi@redhat.com \
--cc=nandinih@linux.ibm.com \
--cc=shuah@kernel.org \
/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®