All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-xfs:iomap-invalidate 4/4] fs/zonefs/super.c:790:3: error: 'ret' undeclared; did you mean
Date: Wed, 22 Jul 2020 00:57:28 +0800	[thread overview]
Message-ID: <202007220025.NORXGojg%lkp@intel.com> (raw)

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

tree:   git://git.infradead.org/users/hch/xfs iomap-invalidate
head:   507f01124bb898462c40ab38fd4c66a38ce70d0a
commit: 507f01124bb898462c40ab38fd4c66a38ce70d0a [4/4] iomap: fall back to buffered writes for invalidation failures
config: alpha-allmodconfig (attached as .config)
compiler: alpha-linux-gcc (GCC) 9.3.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
        git checkout 507f01124bb898462c40ab38fd4c66a38ce70d0a
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=alpha 

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/zonefs/super.c: In function 'zonefs_file_write_iter':
>> fs/zonefs/super.c:790:3: error: 'ret' undeclared (first use in this function); did you mean 'net'?
     790 |   ret = zonefs_file_dio_write(iocb, from);
         |   ^~~
         |   net
   fs/zonefs/super.c:790:3: note: each undeclared identifier is reported only once for each function it appears in

vim +790 fs/zonefs/super.c

   774	
   775	static ssize_t zonefs_file_write_iter(struct kiocb *iocb, struct iov_iter *from)
   776	{
   777		struct inode *inode = file_inode(iocb->ki_filp);
   778	
   779		if (unlikely(IS_IMMUTABLE(inode)))
   780			return -EPERM;
   781	
   782		if (sb_rdonly(inode->i_sb))
   783			return -EROFS;
   784	
   785		/* Write operations beyond the zone size are not allowed */
   786		if (iocb->ki_pos >= ZONEFS_I(inode)->i_max_size)
   787			return -EFBIG;
   788	
   789		if (iocb->ki_flags & IOCB_DIRECT) {
 > 790			ret = zonefs_file_dio_write(iocb, from);
   791			if (ret != -ENOTBLK)
   792				return ret;
   793		}
   794	
   795		return zonefs_file_buffered_write(iocb, from);
   796	}
   797	

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

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

                 reply	other threads:[~2020-07-21 16:57 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=202007220025.NORXGojg%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.