From: kernel test robot <lkp@intel.com>
To: Paul Lawrence <paullawrence@google.com>,
Miklos Szeredi <miklos@szeredi.hu>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Paul Lawrence <paullawrence@google.com>
Subject: Re: [PATCH v1 1/2] fuse: Add backing file option to lookup
Date: Wed, 18 Jun 2025 21:46:25 +0800 [thread overview]
Message-ID: <202506182126.iGTKLLEc-lkp@intel.com> (raw)
In-Reply-To: <20250617221456.888231-2-paullawrence@google.com>
Hi Paul,
kernel test robot noticed the following build errors:
[auto build test ERROR on mszeredi-fuse/for-next]
[also build test ERROR on linus/master v6.16-rc2 next-20250618]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Paul-Lawrence/fuse-Add-backing-file-option-to-lookup/20250618-061717
base: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
patch link: https://lore.kernel.org/r/20250617221456.888231-2-paullawrence%40google.com
patch subject: [PATCH v1 1/2] fuse: Add backing file option to lookup
config: i386-randconfig-001-20250618 (https://download.01.org/0day-ci/archive/20250618/202506182126.iGTKLLEc-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250618/202506182126.iGTKLLEc-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/202506182126.iGTKLLEc-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
fs/fuse/inode.c: In function 'fuse_inode_backing_eq':
>> fs/fuse/inode.c:479:44: error: 'struct fuse_inode' has no member named 'backing_inode'
479 | && fii->backing_inode == fi->backing_inode;
| ^~
>> fs/fuse/inode.c:480:1: warning: control reaches end of non-void function [-Wreturn-type]
480 | }
| ^
vim +479 fs/fuse/inode.c
471
472 static int fuse_inode_backing_eq(struct inode *inode, void *_nodeidp)
473 {
474 struct fuse_inode_identifier *fii =
475 (struct fuse_inode_identifier *) _nodeidp;
476 struct fuse_inode *fi = get_fuse_inode(inode);
477
478 return fii->nodeid == fi->nodeid
> 479 && fii->backing_inode == fi->backing_inode;
> 480 }
481
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-06-18 13:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 22:14 [PATCH v1 0/2] RFC: Extend fuse-passthrough to directories Paul Lawrence
2025-06-17 22:14 ` [PATCH v1 1/2] fuse: Add backing file option to lookup Paul Lawrence
2025-06-18 13:46 ` kernel test robot [this message]
2025-06-17 22:14 ` [PATCH v1 2/2] fuse: open/close backing file Paul Lawrence
2025-06-18 11:01 ` [PATCH v1 0/2] RFC: Extend fuse-passthrough to directories Amir Goldstein
2025-06-19 19:50 ` Paul Lawrence
2025-06-19 20:29 ` Amir Goldstein
2025-07-14 15:20 ` Amir Goldstein
2025-07-22 21:13 ` Paul Lawrence
2025-07-23 16:53 ` Amir Goldstein
2025-07-23 18:30 ` Paul Lawrence
2025-07-24 19:51 ` Amir Goldstein
2025-08-04 17:32 ` [PATCH 0/2] RFC: Set backing file at lookup Paul Lawrence
2025-08-04 17:32 ` [PATCH 1/2] fuse: Allow backing file to be set at lookup (WIP) Paul Lawrence
2025-08-10 14:21 ` Amir Goldstein
2025-08-04 17:32 ` [PATCH 2/2] fuse: Add passthrough for mkdir and rmdir (WIP) Paul Lawrence
2025-08-10 15:40 ` Amir Goldstein
2025-08-10 13:25 ` [PATCH 0/2] RFC: Set backing file at lookup Amir Goldstein
2025-08-10 14:32 ` Amir Goldstein
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=202506182126.iGTKLLEc-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paullawrence@google.com \
/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;
as well as URLs for NNTP newsgroup(s).