public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Harmstone <maharmstone@meta.com>
To: kernel test robot <lkp@intel.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH 09/10] btrfs: move existing remaps before relocating block group
Date: Fri, 16 May 2025 11:43:37 +0000	[thread overview]
Message-ID: <9cfe187c-efce-4449-be3c-72ea584b13f9@meta.com> (raw)
In-Reply-To: <202505161726.w1lqCZxG-lkp@intel.com>

Kernel bot is saying here that I'm relying on 64-bit modulo even on 
32-bit processors, which is easy enough to sort for the actual patch series.

On 16/5/25 10:42, kernel test robot wrote:
> > 
> Hi Mark,
> 
> [This is a private test report for your RFC patch.]
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on kdave/for-next]
> [also build test ERROR on next-20250515]
> [cannot apply to linus/master v6.15-rc6]
> [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://urldefense.com/v3/__https://git-scm.com/docs/git-format-patch*_base_tree_information__;Iw!!Bt8RZUm9aw!62MBgtgUBKJiRzdqPxiQTuw-_8GZHkeBKL3gkYvxPzAhENOx0BjCPNqmDBzj50VZzLPMMjlG$ ]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Mark-Harmstone/btrfs-add-definitions-and-constants-for-remap-tree/20250516-003914
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git  for-next
> patch link:    https://lore.kernel.org/r/20250515163641.3449017-10-maharmstone%40fb.com
> patch subject: [RFC PATCH 09/10] btrfs: move existing remaps before relocating block group
> config: i386-buildonly-randconfig-002-20250516 (https://urldefense.com/v3/__https://download.01.org/0day-ci/archive/20250516/202505161726.w1lqCZxG-lkp@intel.com/config__;!!Bt8RZUm9aw!62MBgtgUBKJiRzdqPxiQTuw-_8GZHkeBKL3gkYvxPzAhENOx0BjCPNqmDBzj50VZzMhIuygf$ )
> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> reproduce (this is a W=1 build): (https://urldefense.com/v3/__https://download.01.org/0day-ci/archive/20250516/202505161726.w1lqCZxG-lkp@intel.com/reproduce__;!!Bt8RZUm9aw!62MBgtgUBKJiRzdqPxiQTuw-_8GZHkeBKL3gkYvxPzAhENOx0BjCPNqmDBzj50VZzNUkCx9l$ )
> 
> 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/202505161726.w1lqCZxG-lkp@intel.com/
> 
> All errors (new ones prefixed by >>, old ones prefixed by <<):
> 
>>> ERROR: modpost: "__umoddi3" [fs/btrfs/btrfs.ko] undefined!
> 


  parent reply	other threads:[~2025-05-16 11:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 16:36 [RFC PATCH 00/10] Remap tree Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 01/10] btrfs: add definitions and constants for remap-tree Mark Harmstone
2025-05-21 12:43   ` Johannes Thumshirn
2025-05-23 13:06     ` Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 02/10] btrfs: add REMAP chunk type Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 03/10] btrfs: allow remapped chunks to have zero stripes Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 04/10] btrfs: add extended version of struct block_group_item Mark Harmstone
2025-05-23  9:53   ` Qu Wenruo
2025-05-23 12:00     ` Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 05/10] btrfs: allow mounting filesystems with remap-tree incompat flag Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 06/10] btrfs: redirect I/O for remapped block groups Mark Harmstone
2025-05-23 10:09   ` Qu Wenruo
2025-05-23 11:53     ` Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 07/10] btrfs: handle deletions from remapped block group Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 08/10] btrfs: handle setting up relocation of block group with remap-tree Mark Harmstone
2025-05-15 16:36 ` [RFC PATCH 09/10] btrfs: move existing remaps before relocating block group Mark Harmstone
     [not found]   ` <202505161726.w1lqCZxG-lkp@intel.com>
2025-05-16 11:43     ` Mark Harmstone [this message]
2025-05-15 16:36 ` [RFC PATCH 10/10] btrfs: replace identity maps with actual remaps when doing relocations Mark Harmstone
2025-05-21  0:04   ` Boris Burkov
2025-05-23 14:54     ` Mark Harmstone

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=9cfe187c-efce-4449-be3c-72ea584b13f9@meta.com \
    --to=maharmstone@meta.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lkp@intel.com \
    /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