From: kernel test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
fuse-devel@lists.sourceforge.net
Subject: [mszeredi-fuse:extent-map 15/18] fs/fuse/inode.c:438:44: error: no member named 'vdax' in 'struct fuse_conn'
Date: Wed, 23 Sep 2026 08:24:48 +0200 [thread overview]
Message-ID: <202609230803.9KZ4KBNg-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git extent-map
head: 70caed148725b4dd32916ecfe906977e2f79aff1
commit: 343c66361a8e8ab509910030bf19eab3357555b2 [15/18] fuse: add support for opening dax device as backing
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260923/202609230803.9KZ4KBNg-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260923/202609230803.9KZ4KBNg-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/202609230803.9KZ4KBNg-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/fuse/inode.c:438:44: error: no member named 'vdax' in 'struct fuse_conn'
438 | if ((attr->flags & FUSE_ATTR_DAX) && !fc->vdax) {
| ~~ ^
1 error generated.
vim +438 fs/fuse/inode.c
409
410 static void fuse_init_inode(struct inode *inode, struct fuse_attr *attr,
411 struct fuse_conn *fc)
412 {
413 inode->i_mode = attr->mode & S_IFMT;
414 inode->i_size = attr->size;
415 inode_set_mtime(inode, attr->mtime, attr->mtimensec);
416 inode_set_ctime(inode, attr->ctime, attr->ctimensec);
417 if (S_ISREG(inode->i_mode)) {
418 fuse_init_common(inode);
419 fuse_init_file_inode(inode, attr->flags);
420 } else if (S_ISDIR(inode->i_mode))
421 fuse_init_dir(inode);
422 else if (S_ISLNK(inode->i_mode))
423 fuse_init_symlink(inode);
424 else if (S_ISCHR(inode->i_mode) || S_ISBLK(inode->i_mode) ||
425 S_ISFIFO(inode->i_mode) || S_ISSOCK(inode->i_mode)) {
426 fuse_init_common(inode);
427 init_special_inode(inode, inode->i_mode,
428 new_decode_dev(attr->rdev));
429 } else
430 BUG();
431 /*
432 * Ensure that we don't cache acls for daemons without FUSE_POSIX_ACL
433 * so they see the exact same behavior as before.
434 */
435 if (!fc->posix_acl)
436 inode->i_acl = inode->i_default_acl = ACL_DONT_CACHE;
437
> 438 if ((attr->flags & FUSE_ATTR_DAX) && !fc->vdax) {
439 inode->i_flags |= S_DAX;
440 inode->i_data.a_ops = &fuse_dax_aops;
441 }
442 }
443
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-23 6:24 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=202609230803.9KZ4KBNg-lkp@intel.com \
--to=lkp@intel.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=llvm@lists.linux.dev \
--cc=mszeredi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox