All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Christian Brauner <christianvanbrauner@gmail.com>,
	Christian Brauner <brauner@kernel.org>,
	Jeff Layton <jlayton@kernel.org>
Subject: [brauner-vfs:vfs.netfs 59/64] fs/netfs/buffered_write.c:520:17: error: implicit declaration of function 'generic_error_remove_folio'; did you mean 'generic_error_remove_page'?
Date: Sat, 16 Dec 2023 07:17:58 +0800	[thread overview]
Message-ID: <202312160746.MkBo6D2w-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.netfs
head:   361e796134214b255d35dd801451b40a68c34e11
commit: 02bf7b4afdba5ec3abddb70d5184666b97506e56 [59/64] netfs: Provide a writepages implementation
config: i386-buildonly-randconfig-006-20231216 (https://download.01.org/0day-ci/archive/20231216/202312160746.MkBo6D2w-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231216/202312160746.MkBo6D2w-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/202312160746.MkBo6D2w-lkp@intel.com/

All errors (new ones prefixed by >>):

   fs/netfs/buffered_write.c: In function 'netfs_kill_pages':
>> fs/netfs/buffered_write.c:520:17: error: implicit declaration of function 'generic_error_remove_folio'; did you mean 'generic_error_remove_page'? [-Werror=implicit-function-declaration]
     520 |                 generic_error_remove_folio(mapping, folio);
         |                 ^~~~~~~~~~~~~~~~~~~~~~~~~~
         |                 generic_error_remove_page
   cc1: some warnings being treated as errors


vim +520 fs/netfs/buffered_write.c

   490	
   491	/*
   492	 * Kill all the pages in the given range
   493	 */
   494	static void netfs_kill_pages(struct address_space *mapping,
   495				     loff_t start, loff_t len)
   496	{
   497		struct folio *folio;
   498		pgoff_t index = start / PAGE_SIZE;
   499		pgoff_t last = (start + len - 1) / PAGE_SIZE, next;
   500	
   501		_enter("%llx-%llx", start, start + len - 1);
   502	
   503		do {
   504			_debug("kill %lx (to %lx)", index, last);
   505	
   506			folio = filemap_get_folio(mapping, index);
   507			if (IS_ERR(folio)) {
   508				next = index + 1;
   509				continue;
   510			}
   511	
   512			next = folio_next_index(folio);
   513	
   514			trace_netfs_folio(folio, netfs_folio_trace_kill);
   515			folio_clear_uptodate(folio);
   516			if (folio_test_fscache(folio))
   517				folio_end_fscache(folio);
   518			folio_end_writeback(folio);
   519			folio_lock(folio);
 > 520			generic_error_remove_folio(mapping, folio);
   521			folio_unlock(folio);
   522			folio_put(folio);
   523	
   524		} while (index = next, index <= last);
   525	
   526		_leave("");
   527	}
   528	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2023-12-15 23:18 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=202312160746.MkBo6D2w-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brauner@kernel.org \
    --cc=christianvanbrauner@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=jlayton@kernel.org \
    --cc=oe-kbuild-all@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.