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,
	linux-kernel@vger.kernel.org
Subject: [dhowells-fs:fscache-rewrite 65/69] fs/nfs/file.c:435:9: error: implicit declaration of function 'nfs_fscache_release_page'
Date: Fri, 10 Dec 2021 10:43:03 +0800	[thread overview]
Message-ID: <202112101053.5YQV0dqW-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git fscache-rewrite
head:   82abe23a0865faea23cf06ac51f2303f26b9bb53
commit: f6770459bb519747a01e91834f88ac82299a47de [65/69] nfs: Implement cache I/O by accessing the cache directly
config: x86_64-randconfig-a011-20211209 (https://download.01.org/0day-ci/archive/20211210/202112101053.5YQV0dqW-lkp@intel.com/config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 097a1cb1d5ebb3a0ec4bcaed8ba3ff6a8e33c00a)
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://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?id=f6770459bb519747a01e91834f88ac82299a47de
        git remote add dhowells-fs https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
        git fetch --no-tags dhowells-fs fscache-rewrite
        git checkout f6770459bb519747a01e91834f88ac82299a47de
        # 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=x86_64 SHELL=/bin/bash fs/nfs/

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/nfs/file.c:87:2: error: implicit declaration of function 'nfs_fscache_release_file' [-Werror,-Wimplicit-function-declaration]
           nfs_fscache_release_file(inode, filp);
           ^
   fs/nfs/file.c:87:2: note: did you mean 'nfs_fscache_open_file'?
   fs/nfs/fscache.h:130:20: note: 'nfs_fscache_open_file' declared here
   static inline void nfs_fscache_open_file(struct inode *inode,
                      ^
>> fs/nfs/file.c:435:9: error: implicit declaration of function 'nfs_fscache_release_page' [-Werror,-Wimplicit-function-declaration]
           return nfs_fscache_release_page(page, gfp);
                  ^
   2 errors generated.


vim +/nfs_fscache_release_page +435 fs/nfs/file.c

cd52ed35535ef4 Trond Myklebust 2006-03-20  421  
6b9b3514aa1881 David Howells   2009-04-03  422  /*
6b9b3514aa1881 David Howells   2009-04-03  423   * Attempt to release the private state associated with a page
545db45f0fc0d4 David Howells   2009-04-03  424   * - Called if either PG_private or PG_fscache is set on the page
6b9b3514aa1881 David Howells   2009-04-03  425   * - Caller holds page lock
6b9b3514aa1881 David Howells   2009-04-03  426   * - Return true (may release page) or false (may not)
6b9b3514aa1881 David Howells   2009-04-03  427   */
cd52ed35535ef4 Trond Myklebust 2006-03-20  428  static int nfs_release_page(struct page *page, gfp_t gfp)
cd52ed35535ef4 Trond Myklebust 2006-03-20  429  {
b7eaefaa8722fd Chuck Lever     2008-06-11  430  	dfprintk(PAGECACHE, "NFS: release_page(%p)\n", page);
b7eaefaa8722fd Chuck Lever     2008-06-11  431  
e3db7691e9f3df Trond Myklebust 2007-01-10  432  	/* If PagePrivate() is set, then the page is not freeable */
545db45f0fc0d4 David Howells   2009-04-03  433  	if (PagePrivate(page))
ddeff520f02b92 Nikita Danilov  2006-08-09  434  		return 0;
545db45f0fc0d4 David Howells   2009-04-03 @435  	return nfs_fscache_release_page(page, gfp);
e3db7691e9f3df Trond Myklebust 2007-01-10  436  }
e3db7691e9f3df Trond Myklebust 2007-01-10  437  

:::::: The code at line 435 was first introduced by commit
:::::: 545db45f0fc0d4203b045047798ce156972a3056 NFS: FS-Cache page management

:::::: TO: David Howells <dhowells@redhat.com>
:::::: CC: David Howells <dhowells@redhat.com>

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

                 reply	other threads:[~2021-12-10  2:43 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=202112101053.5YQV0dqW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --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