From: kernel test robot <lkp@intel.com>
To: Miklos Szeredi <mszeredi@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, fuse-devel@lists.sourceforge.net,
Amir Goldstein <amir73il@gmail.com>
Subject: [mszeredi-fuse:extent-map-v3 28/29] fs/fuse/ext_map.c:150:23: warning: unused variable 'pfn'
Date: Tue, 06 Oct 2026 22:27:55 +0200 [thread overview]
Message-ID: <202610062207.LQIBA0hv-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git extent-map-v3
head: abdbd9557c238384900ebd545f426a609e0162ae
commit: 91fc78ad913efd321396e414a561474c9072d334 [28/29] fuse: add extent map I/O support
config: nios2-randconfig-r2106-20261006 (https://download.01.org/0day-ci/archive/20261006/202610062207.LQIBA0hv-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261006/202610062207.LQIBA0hv-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/202610062207.LQIBA0hv-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/fuse/ext_map.c: In function 'fuse_ext_map_huge_fault':
>> fs/fuse/ext_map.c:150:23: warning: unused variable 'pfn' [-Wunused-variable]
150 | unsigned long pfn;
| ^~~
At top level:
>> fs/fuse/ext_map.c:141:31: warning: 'fuse_ext_map_iomap_ops' defined but not used [-Wunused-const-variable=]
141 | static const struct iomap_ops fuse_ext_map_iomap_ops = {
| ^~~~~~~~~~~~~~~~~~~~~~
vim +/pfn +150 fs/fuse/ext_map.c
140
> 141 static const struct iomap_ops fuse_ext_map_iomap_ops = {
142 .iomap_begin = fuse_ext_map_iomap_begin,
143 };
144
145 static vm_fault_t fuse_ext_map_huge_fault(struct vm_fault *vmf, unsigned int order)
146 {
147 struct inode *inode = file_inode(vmf->vma->vm_file);
148 bool write_fault = (vmf->flags & FAULT_FLAG_WRITE) && (vmf->vma->vm_flags & VM_SHARED);
149 vm_fault_t ret;
> 150 unsigned long pfn;
151
152 if (WARN_ON_ONCE(!IS_DAX(inode)))
153 return VM_FAULT_SIGBUS;
154
155 if (write_fault) {
156 sb_start_pagefault(inode->i_sb);
157 file_update_time(vmf->vma->vm_file);
158 }
159
160 filemap_invalidate_lock_shared(inode->i_mapping);
161
162 ret = dax_iomap_fault(vmf, order, &pfn, NULL, &fuse_ext_map_iomap_ops);
163 if (ret & VM_FAULT_NEEDDSYNC)
164 ret = dax_finish_sync_fault(vmf, order, pfn);
165
166 filemap_invalidate_unlock_shared(inode->i_mapping);
167
168 if (write_fault)
169 sb_end_pagefault(inode->i_sb);
170
171 return ret;
172 }
173
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-06 20:28 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=202610062207.LQIBA0hv-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--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 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.