public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Mark Harmstone <maharmstone@fb.com>, linux-btrfs@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Mark Harmstone <maharmstone@fb.com>
Subject: Re: [PATCH 11/12] btrfs: move existing remaps before relocating block group
Date: Fri, 6 Jun 2025 19:20:56 +0800	[thread overview]
Message-ID: <202506061952.ALl7BezR-lkp@intel.com> (raw)
In-Reply-To: <20250605162345.2561026-12-maharmstone@fb.com>

Hi Mark,

kernel test robot noticed the following build warnings:

[auto build test WARNING on kdave/for-next]
[also build test WARNING on linus/master next-20250606]
[cannot apply to v6.15]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Mark-Harmstone/btrfs-add-definitions-and-constants-for-remap-tree/20250606-002804
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-next
patch link:    https://lore.kernel.org/r/20250605162345.2561026-12-maharmstone%40fb.com
patch subject: [PATCH 11/12] btrfs: move existing remaps before relocating block group
config: csky-randconfig-r133-20250606 (https://download.01.org/0day-ci/archive/20250606/202506061952.ALl7BezR-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.3.0
reproduce: (https://download.01.org/0day-ci/archive/20250606/202506061952.ALl7BezR-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/202506061952.ALl7BezR-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> fs/btrfs/relocation.c:4036:27: sparse: sparse: incorrect type in initializer (different base types) @@     expected int op @@     got restricted blk_opf_t @@
   fs/btrfs/relocation.c:4036:27: sparse:     expected int op
   fs/btrfs/relocation.c:4036:27: sparse:     got restricted blk_opf_t
>> fs/btrfs/relocation.c:4042:46: sparse: sparse: incorrect type in argument 2 (different base types) @@     expected restricted blk_opf_t [usertype] opf @@     got int op @@
   fs/btrfs/relocation.c:4042:46: sparse:     expected restricted blk_opf_t [usertype] opf
   fs/btrfs/relocation.c:4042:46: sparse:     got int op
   fs/btrfs/relocation.c:4053:62: sparse: sparse: incorrect type in argument 2 (different base types) @@     expected restricted blk_opf_t [usertype] opf @@     got int op @@
   fs/btrfs/relocation.c:4053:62: sparse:     expected restricted blk_opf_t [usertype] opf
   fs/btrfs/relocation.c:4053:62: sparse:     got int op

vim +4036 fs/btrfs/relocation.c

  4028	
  4029	static int copy_remapped_data_io(struct btrfs_fs_info *fs_info,
  4030					 struct reloc_io_private *priv,
  4031					 struct page **pages, u64 addr, u64 length,
  4032					 bool do_write)
  4033	{
  4034		struct btrfs_bio *bbio;
  4035		unsigned long i = 0;
> 4036		int op = do_write ? REQ_OP_WRITE : REQ_OP_READ;
  4037	
  4038		init_completion(&priv->done);
  4039		refcount_set(&priv->pending_refs, 1);
  4040		priv->status = 0;
  4041	
> 4042		bbio = btrfs_bio_alloc(BIO_MAX_VECS, op, fs_info, reloc_endio,
  4043				       priv);
  4044		bbio->bio.bi_iter.bi_sector = addr >> SECTOR_SHIFT;
  4045	
  4046		do {
  4047			size_t bytes = min_t(u64, length, PAGE_SIZE);
  4048	
  4049			if (bio_add_page(&bbio->bio, pages[i], bytes, 0) < bytes) {
  4050				refcount_inc(&priv->pending_refs);
  4051				btrfs_submit_bbio(bbio, 0);
  4052	
  4053				bbio = btrfs_bio_alloc(BIO_MAX_VECS, op, fs_info,
  4054						       reloc_endio, priv);
  4055				bbio->bio.bi_iter.bi_sector = addr >> SECTOR_SHIFT;
  4056				continue;
  4057			}
  4058	
  4059			i++;
  4060			addr += bytes;
  4061			length -= bytes;
  4062		} while (length);
  4063	
  4064		refcount_inc(&priv->pending_refs);
  4065		btrfs_submit_bbio(bbio, 0);
  4066	
  4067		if (!refcount_dec_and_test(&priv->pending_refs))
  4068			wait_for_completion_io(&priv->done);
  4069	
  4070		return blk_status_to_errno(READ_ONCE(priv->status));
  4071	}
  4072	

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

  reply	other threads:[~2025-06-06 11:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05 16:23 [PATCH 00/12] btrfs: remap tree Mark Harmstone
2025-06-05 16:23 ` [PATCH 01/12] btrfs: add definitions and constants for remap-tree Mark Harmstone
2025-06-13 21:02   ` Boris Burkov
2025-06-05 16:23 ` [PATCH 02/12] btrfs: add REMAP chunk type Mark Harmstone
2025-06-13 21:22   ` Boris Burkov
2025-06-05 16:23 ` [PATCH 03/12] btrfs: allow remapped chunks to have zero stripes Mark Harmstone
2025-06-13 21:41   ` Boris Burkov
2025-08-08 14:12     ` Mark Harmstone
2025-06-05 16:23 ` [PATCH 04/12] btrfs: remove remapped block groups from the free-space tree Mark Harmstone
2025-06-06  6:41   ` kernel test robot
2025-06-13 22:00   ` Boris Burkov
2025-08-12 14:50     ` Mark Harmstone
2025-06-05 16:23 ` [PATCH 05/12] btrfs: don't add metadata items for the remap tree to the extent tree Mark Harmstone
2025-06-13 22:39   ` Boris Burkov
2025-06-05 16:23 ` [PATCH 06/12] btrfs: add extended version of struct block_group_item Mark Harmstone
2025-06-05 16:23 ` [PATCH 07/12] btrfs: allow mounting filesystems with remap-tree incompat flag Mark Harmstone
2025-06-05 16:23 ` [PATCH 08/12] btrfs: redirect I/O for remapped block groups Mark Harmstone
2025-06-05 16:23 ` [PATCH 09/12] btrfs: handle deletions from remapped block group Mark Harmstone
2025-06-13 23:42   ` Boris Burkov
2025-08-11 16:48     ` Mark Harmstone
2025-08-11 16:59     ` Mark Harmstone
2025-06-05 16:23 ` [PATCH 10/12] btrfs: handle setting up relocation of block group with remap-tree Mark Harmstone
2025-06-13 23:25   ` Boris Burkov
2025-08-12 11:20     ` Mark Harmstone
2025-06-05 16:23 ` [PATCH 11/12] btrfs: move existing remaps before relocating block group Mark Harmstone
2025-06-06 11:20   ` kernel test robot [this message]
2025-06-05 16:23 ` [PATCH 12/12] btrfs: replace identity maps with actual remaps when doing relocations Mark Harmstone
2025-06-05 16:43 ` [PATCH 00/12] btrfs: remap tree Jonah Sabean
2025-06-06 13:35   ` Mark Harmstone
2025-06-09 16:05     ` Anand Jain
2025-06-09 18:51 ` David Sterba
2025-06-10  9:19   ` Mark Harmstone
2025-06-10 14:31 ` Mark Harmstone
2025-06-10 23:56   ` Qu Wenruo
2025-06-11  8:06     ` Mark Harmstone
2025-06-11 15:28 ` Mark Harmstone
2025-06-14  0:04 ` Boris Burkov
2025-06-26 22:10 ` Mark Harmstone
2025-06-27  5:59   ` Neal Gompa

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=202506061952.ALl7BezR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=maharmstone@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox