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
Subject: [dhowells-fs:netfs-writeback 30/30] fs/cachefiles/io.c:640:31: error: 'BIO_MAX_VECS' undeclared; did you mean 'BIO_MAX_SECTORS'?
Date: Fri, 1 Mar 2024 01:10:20 +0800	[thread overview]
Message-ID: <202403010140.MEEg8Qua-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git netfs-writeback
head:   afd4a14c1f0fde0fd833c3d1984c4ebb5981f7f8
commit: 920c10a555e2742546325940063cadc115de6a08 [30/30] netfs: Use writeback_iter()
config: nios2-randconfig-001-20240229 (https://download.01.org/0day-ci/archive/20240301/202403010140.MEEg8Qua-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240301/202403010140.MEEg8Qua-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/202403010140.MEEg8Qua-lkp@intel.com/

All errors (new ones prefixed by >>):

   fs/cachefiles/io.c: In function 'cachefiles_preprepare_write':
>> fs/cachefiles/io.c:640:31: error: 'BIO_MAX_VECS' undeclared (first use in this function); did you mean 'BIO_MAX_SECTORS'?
     640 |         subreq->max_nr_segs = BIO_MAX_VECS;
         |                               ^~~~~~~~~~~~
         |                               BIO_MAX_SECTORS
   fs/cachefiles/io.c:640:31: note: each undeclared identifier is reported only once for each function it appears in


vim +640 fs/cachefiles/io.c

   624	
   625	static int cachefiles_preprepare_write(struct netfs_io_subrequest *subreq)
   626	{
   627		struct netfs_io_request *wreq = subreq->rreq;
   628		struct netfs_cache_resources *cres = &wreq->cache_resources;
   629	
   630		_enter("W=%x[%x] %llx", wreq->debug_id, subreq->debug_index, subreq->start);
   631	
   632		if (!cachefiles_cres_file(cres)) {
   633			if (!fscache_wait_for_operation(cres, FSCACHE_WANT_WRITE))
   634				return -ENOBUFS;
   635			if (!cachefiles_cres_file(cres))
   636				return -ENOBUFS;
   637		}
   638	
   639		subreq->max_len = 16384; //ULONG_MAX;
 > 640		subreq->max_nr_segs = BIO_MAX_VECS;
   641		return 0;
   642	}
   643	

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

                 reply	other threads:[~2024-02-29 17:13 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=202403010140.MEEg8Qua-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dhowells@redhat.com \
    --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.