public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
	GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
	linux-kernel@vger.kernel.org
Subject: [ammarfaizi2-block:dhowells/linux-fs/netfs-maple 25/35] fs/fs-writeback.c:2789:2: error: implicit declaration of function 'wbc_attach_unlock_fdatawrite_inode'
Date: Fri, 11 Feb 2022 14:35:33 +0800	[thread overview]
Message-ID: <202202111418.cjJuXYM8-lkp@intel.com> (raw)

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: arm-colibri_pxa270_defconfig (https://download.01.org/0day-ci/archive/20220211/202202111418.cjJuXYM8-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project f6685f774697c85d6a352dcea013f46a99f9fe31)
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
        # install arm cross compiling tool for clang build
        # apt-get install binutils-arm-linux-gnueabi
        # 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=clang make.cross W=1 O=build_dir ARCH=arm 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:2789:2: error: implicit declaration of function 'wbc_attach_unlock_fdatawrite_inode' [-Werror,-Wimplicit-function-declaration]
           wbc_attach_unlock_fdatawrite_inode(wbc, inode);
           ^
   fs/fs-writeback.c:2789:2: note: did you mean 'wbc_attach_fdatawrite_inode'?
   include/linux/writeback.h:325:20: note: 'wbc_attach_fdatawrite_inode' declared here
   static inline void wbc_attach_fdatawrite_inode(struct writeback_control *wbc,
                      ^
   1 error generated.


vim +/wbc_attach_unlock_fdatawrite_inode +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

                 reply	other threads:[~2022-02-11  6:36 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=202202111418.cjJuXYM8-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=gwml@vger.gnuweeb.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@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