From: kernel test robot <lkp@intel.com>
To: Shivank Garg <shivankg@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-unstable 272/272] fs/jfs/jfs_metapage.c:238:28: error: called object type 'void *' is not a function or function pointer
Date: Fri, 2 May 2025 05:12:28 +0800 [thread overview]
Message-ID: <202505020532.eOaIqKwc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: ea17e4fdc13cae144d90ce8561c2f50a49492037
commit: ea17e4fdc13cae144d90ce8561c2f50a49492037 [272/272] jfs: implement migrate_folio for jfs_metapage_aops
config: arm-randconfig-004-20250502 (https://download.01.org/0day-ci/archive/20250502/202505020532.eOaIqKwc-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250502/202505020532.eOaIqKwc-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/202505020532.eOaIqKwc-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/jfs/jfs_metapage.c:238:28: error: called object type 'void *' is not a function or function pointer
238 | rc = filemap_migrate_folio(mapping, dst, src, mode);
| ~~~~~~~~~~~~~~~~~~~~~^
fs/jfs/jfs_metapage.c:641:31: error: called object type 'void *' is not a function or function pointer
641 | return filemap_migrate_folio(mapping, dst, src, mode);
| ~~~~~~~~~~~~~~~~~~~~~^
2 errors generated.
vim +238 fs/jfs/jfs_metapage.c
226
227 static int __metapage_migrate_folio(struct address_space *mapping, struct folio *dst,
228 struct folio *src, enum migrate_mode mode)
229 {
230 struct metapage *mp;
231 int page_offset;
232 int rc;
233
234 mp = folio_to_mp(src, 0);
235 if (mp && metapage_locked(mp))
236 return -EAGAIN;
237
> 238 rc = filemap_migrate_folio(mapping, dst, src, mode);
239 if (rc != MIGRATEPAGE_SUCCESS)
240 return rc;
241
242 if (unlikely(insert_metapage(dst, mp)))
243 return -EAGAIN;
244
245 page_offset = mp->data - folio_address(src);
246 mp->data = folio_address(dst) + page_offset;
247 mp->folio = dst;
248 remove_metapage(src, mp);
249
250 return MIGRATEPAGE_SUCCESS;
251 }
252
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-01 21:12 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=202505020532.eOaIqKwc-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shivankg@amd.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).