linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [dhowells-fs:fscache-iter-2 2/67] fs/fscache/io.c:164:5: error: no previous prototype for '__fscache_fallback_read_page'
Date: Wed, 29 Sep 2021 10:08:50 +0800	[thread overview]
Message-ID: <202109291043.BnplXxV6-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3322 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git fscache-iter-2
head:   23676c28d1a9add6ea09f19ca89b71be994a4b79
commit: b5cd0254309847abfb2eebfbcbd4415d61c5af1b [2/67] fscache: Implement a fallback I/O interface to replace the old API
config: i386-allyesconfig (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/commit/?id=b5cd0254309847abfb2eebfbcbd4415d61c5af1b
        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-iter-2
        git checkout b5cd0254309847abfb2eebfbcbd4415d61c5af1b
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

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/fscache/io.c:164:5: error: no previous prototype for '__fscache_fallback_read_page' [-Werror=missing-prototypes]
     164 | int __fscache_fallback_read_page(struct fscache_cookie *cookie, struct page *page)
         |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> fs/fscache/io.c:194:5: error: no previous prototype for '__fscache_fallback_write_page' [-Werror=missing-prototypes]
     194 | int __fscache_fallback_write_page(struct fscache_cookie *cookie, struct page *page)
         |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   fs/fscache/io.c: In function '__fscache_fallback_write_page':
>> fs/fscache/io.c:200:9: error: variable 'len' set but not used [-Werror=unused-but-set-variable]
     200 |  size_t len;
         |         ^~~
>> fs/fscache/io.c:199:9: error: variable 'start' set but not used [-Werror=unused-but-set-variable]
     199 |  loff_t start;
         |         ^~~~~
   cc1: all warnings being treated as errors


vim +/__fscache_fallback_read_page +164 fs/fscache/io.c

   160	
   161	/*
   162	 * Fallback page reading interface.
   163	 */
 > 164	int __fscache_fallback_read_page(struct fscache_cookie *cookie, struct page *page)
   165	{
   166		struct netfs_cache_resources cres;
   167		struct iov_iter iter;
   168		struct bio_vec bvec[1];
   169		int ret;
   170	
   171		_enter("%lx", page->index);
   172	
   173		memset(&cres, 0, sizeof(cres));
   174		bvec[0].bv_page		= page;
   175		bvec[0].bv_offset	= 0;
   176		bvec[0].bv_len		= PAGE_SIZE;
   177		iov_iter_bvec(&iter, READ, bvec, ARRAY_SIZE(bvec), PAGE_SIZE);
   178	
   179		ret = fscache_begin_read_operation(&cres, cookie);
   180		if (ret < 0)
   181			return ret;
   182	
   183		ret = fscache_read(&cres, page_offset(page), &iter, NETFS_READ_HOLE_FAIL,
   184				   NULL, NULL);
   185		fscache_end_operation(&cres);
   186		_leave(" = %d", ret);
   187		return ret;
   188	}
   189	EXPORT_SYMBOL(__fscache_fallback_read_page);
   190	
   191	/*
   192	 * Fallback page writing interface.
   193	 */
 > 194	int __fscache_fallback_write_page(struct fscache_cookie *cookie, struct page *page)
   195	{
   196		struct netfs_cache_resources cres;
   197		struct iov_iter iter;
   198		struct bio_vec bvec[1];
 > 199		loff_t start;
 > 200		size_t len;

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

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 66015 bytes --]

                 reply	other threads:[~2021-09-29  2:09 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=202109291043.BnplXxV6-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).