All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [djwong-xfs:zoned 125/144] fs/xfs/xfs_zone_alloc.c:669:62: sparse: sparse: incorrect type in argument 1 (different base types)
Date: Mon, 23 Dec 2024 05:00:08 +0800	[thread overview]
Message-ID: <202412230407.FNn45tup-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git zoned
head:   e438c133cc544cff3b44f8c3fde87a8ab5f8a3de
commit: aeba972d7108ff837bdc8786fd19f786f9dbd3ba [125/144] xfs: add the zoned space allocator
config: x86_64-randconfig-r132-20241223 (https://download.01.org/0day-ci/archive/20241223/202412230407.FNn45tup-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241223/202412230407.FNn45tup-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/202412230407.FNn45tup-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/xfs/xfs_zone_alloc.c:669:62: sparse: sparse: incorrect type in argument 1 (different base types) @@     expected restricted blk_status_t [usertype] status @@     got long @@
   fs/xfs/xfs_zone_alloc.c:669:62: sparse:     expected restricted blk_status_t [usertype] status
   fs/xfs/xfs_zone_alloc.c:669:62: sparse:     got long
>> fs/xfs/xfs_zone_alloc.c:669:33: sparse: sparse: incorrect type in assignment (different base types) @@     expected restricted blk_status_t [usertype] bi_status @@     got int @@
   fs/xfs/xfs_zone_alloc.c:669:33: sparse:     expected restricted blk_status_t [usertype] bi_status
   fs/xfs/xfs_zone_alloc.c:669:33: sparse:     got int

vim +669 fs/xfs/xfs_zone_alloc.c

   621	
   622	void
   623	xfs_zone_alloc_and_submit(
   624		struct iomap_ioend	*ioend,
   625		struct xfs_open_zone	**oz)
   626	{
   627		unsigned int		alloc_len;
   628		struct iomap_ioend	*split;
   629		bool			is_seq;
   630	
   631		if (xfs_is_shutdown(XFS_I(ioend->io_inode)->i_mount))
   632			goto out_error;
   633	
   634		/*
   635		 * If we don't have a cached zone in this write context, see if the
   636		 * last extent before the one we are writing points of an active zone.
   637		 * If so, just continue writing to it.
   638		 */
   639		if (!*oz && ioend->io_offset)
   640			*oz = xfs_last_used_zone(ioend);
   641		if (!*oz) {
   642	select_zone:
   643			*oz = xfs_select_zone(ioend);
   644			if (!*oz)
   645				goto out_error;
   646		}
   647	
   648		alloc_len = xfs_zone_alloc_blocks(ioend, *oz, &is_seq);
   649		if (!alloc_len) {
   650			xfs_open_zone_put(*oz);
   651			goto select_zone;
   652		}
   653	
   654		while ((split = iomap_split_ioend(ioend, alloc_len, is_seq))) {
   655			if (IS_ERR(split))
   656				goto out_split_error;
   657			alloc_len -= split->io_bio.bi_iter.bi_size;
   658			xfs_submit_zoned_bio(split, is_seq);
   659			if (!alloc_len) {
   660				xfs_open_zone_put(*oz);
   661				goto select_zone;
   662			}
   663		}
   664	
   665		xfs_submit_zoned_bio(ioend, is_seq);
   666		return;
   667	
   668	out_split_error:
 > 669		ioend->io_bio.bi_status = blk_status_to_errno(PTR_ERR(split));
   670	out_error:
   671		bio_io_error(&ioend->io_bio);
   672	}
   673	

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

                 reply	other threads:[~2024-12-22 21:00 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=202412230407.FNn45tup-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=darrick.wong@oracle.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.