[ammarfaizi2-block:dhowells/linux-fs/netfs-maple 25/35] fs/fs-writeback.c:2789:9: error: implicit declaration of function 'wbc_attach_unlock_fdatawrite_inode'; did you mean 'wbc_attach_fdatawrite_inode'?

[ammarfaizi2-block:dhowells/linux-fs/netfs-maple 25/35] fs/fs-writeback.c:2789:9: error: implicit declaration of function 'wbc_attach_unlock_fdatawrite_inode'; did you mean 'wbc_attach_fdatawrite_inode'?

[kernel test robot]

tree:   https://github.com/ammarfaizi2/linux-block dhowells/linux-fs/netfs-maple
head:   429e2bb6fb190f390ed23afc0d2308e877c43be5
commit: 9c1befbc079fcef04228d2b67e931f9635d58591 [25/35] vfs: Take I_SYNC whilst performing fsync() and similar
config: arc-defconfig (https://download.01.org/0day-ci/archive/20220211/202202111544.8rMkF0G8-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/ammarfaizi2/linux-block/commit/9c1befbc079fcef04228d2b67e931f9635d58591
        git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
        git fetch --no-tags ammarfaizi2-block dhowells/linux-fs/netfs-maple
        git checkout 9c1befbc079fcef04228d2b67e931f9635d58591
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   fs/fs-writeback.c: In function 'filemap_fdatawrite_wbc':
>> fs/fs-writeback.c:2789:9: error: implicit declaration of function 'wbc_attach_unlock_fdatawrite_inode'; did you mean 'wbc_attach_fdatawrite_inode'? [-Werror=implicit-function-declaration]
    2789 |         wbc_attach_unlock_fdatawrite_inode(wbc, inode);
         |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         |         wbc_attach_fdatawrite_inode
   cc1: some warnings being treated as errors


vim +2789 fs/fs-writeback.c

  2762	
  2763	/**
  2764	 * filemap_fdatawrite_wbc - start writeback on mapping dirty pages in range
  2765	 * @mapping:	address space structure to write
  2766	 * @wbc:	the writeback_control controlling the writeout
  2767	 *
  2768	 * Call writepages on the mapping using the provided wbc to control the
  2769	 * writeout.
  2770	 *
  2771	 * Return: %0 on success, negative error code otherwise.
  2772	 */
  2773	int filemap_fdatawrite_wbc(struct address_space *mapping,
  2774				   struct writeback_control *wbc)
  2775	{
  2776		struct inode *inode = mapping->host;
  2777		int ret;
  2778	
  2779		if (!mapping_can_writeback(mapping) ||
  2780		    !mapping_tagged(mapping, PAGECACHE_TAG_DIRTY))
  2781			return 0;
  2782	
  2783		spin_lock(&inode->i_lock);
  2784		if (inode->i_state & I_SYNC) {
  2785			__inode_wait_for_writeback(inode);
  2786			WARN_ON(inode->i_state & I_SYNC);
  2787		}
  2788	
> 2789		wbc_attach_unlock_fdatawrite_inode(wbc, inode);

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org