mirror of https://lore.kernel.org/lkml/
 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,
	Jeff Layton <jlayton@kernel.org>
Subject: [jlayton:ceph-fscache-rewrite-indexing 2/6] fs/cachefiles/io.c:214:41: error: 'fscache_n_b_writing' undeclared; did you mean 'fscache_write'?
Date: Tue, 2 Nov 2021 03:28:18 +0800	[thread overview]
Message-ID: <202111020311.zEDv142r-lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git ceph-fscache-rewrite-indexing
head:   54d8f4ec911e13051881c8e23628e33054132f41
commit: bbe759e67e26ecc0d2667072d7dafaaa1caf38e2 [2/6] cachefiles: Fix space check to allow for I/O writes
config: arc-buildonly-randconfig-r006-20211101 (attached as .config)
compiler: arceb-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://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git/commit/?id=bbe759e67e26ecc0d2667072d7dafaaa1caf38e2
        git remote add jlayton https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
        git fetch --no-tags jlayton ceph-fscache-rewrite-indexing
        git checkout bbe759e67e26ecc0d2667072d7dafaaa1caf38e2
        # save the attached .config 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 fs/cachefiles/

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/cachefiles/io.c: In function 'cachefiles_write_complete':
>> fs/cachefiles/io.c:214:41: error: 'fscache_n_b_writing' undeclared (first use in this function); did you mean 'fscache_write'?
     214 |         atomic_long_sub(ki->b_writing, &fscache_n_b_writing);
         |                                         ^~~~~~~~~~~~~~~~~~~
         |                                         fscache_write
   fs/cachefiles/io.c:214:41: note: each undeclared identifier is reported only once for each function it appears in
   fs/cachefiles/io.c: In function 'cachefiles_write':
   fs/cachefiles/io.c:273:41: error: 'fscache_n_b_writing' undeclared (first use in this function); did you mean 'fscache_write'?
     273 |         atomic_long_add(ki->b_writing, &fscache_n_b_writing);
         |                                         ^~~~~~~~~~~~~~~~~~~
         |                                         fscache_write


vim +214 fs/cachefiles/io.c

   193	
   194	/*
   195	 * Handle completion of a write to the cache.
   196	 */
   197	static void cachefiles_write_complete(struct kiocb *iocb, long ret, long ret2)
   198	{
   199		struct cachefiles_kiocb *ki = container_of(iocb, struct cachefiles_kiocb, iocb);
   200		struct cachefiles_object *object = ki->object;
   201		struct inode *inode = file_inode(ki->iocb.ki_filp);
   202	
   203		_enter("%ld,%ld", ret, ret2);
   204	
   205		/* Tell lockdep we inherited freeze protection from submission thread */
   206		__sb_writers_acquired(inode->i_sb, SB_FREEZE_WRITE);
   207		__sb_end_write(inode->i_sb, SB_FREEZE_WRITE);
   208	
   209		if (ret < 0)
   210			trace_cachefiles_io_error(object, inode, ret,
   211						  cachefiles_trace_write_error);
   212	
   213		atomic_long_sub(ki->b_writing, &object->volume->cache->b_writing);
 > 214		atomic_long_sub(ki->b_writing, &fscache_n_b_writing);
   215		set_bit(FSCACHE_COOKIE_HAVE_DATA, &object->cookie->flags);
   216		if (ki->term_func)
   217			ki->term_func(ki->term_func_priv, ret, ki->was_async);
   218		cachefiles_put_kiocb(ki);
   219	}
   220	

---
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: 29075 bytes --]

                 reply	other threads:[~2021-11-01 19:37 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=202111020311.zEDv142r-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --cc=jlayton@kernel.org \
    --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

all inboxes | Powered by JetHome®