On Wed, Jun 25, 2025 at 09:48:15AM -0700, Joanne Koong wrote: > On Wed, Jun 25, 2025 at 7:18 AM kernel test robot <lkp@xxxxxxxxx> wrote: > > > > Hi Joanne, > > > > kernel test robot noticed the following build errors: > > > > [auto build test ERROR on brauner-vfs/vfs.all] > > [also build test ERROR on xfs-linux/for-next linus/master v6.16-rc3 next-20250625] > > [cannot apply to gfs2/for-next mszeredi-fuse/for-next] > > [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/Joanne-Koong/iomap-pass-more-arguments-using-struct-iomap_writepage_ctx/20250624-102709 > > base: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all > > patch link: https://lore.kernel.org/r/20250624022135.832899-14-joannelkoong%40gmail.com > > patch subject: [PATCH v3 13/16] fuse: use iomap for writeback > > config: arm64-randconfig-003-20250625 (https://download.01.org/0day-ci/archive/20250625/202506252117.9V3HTO0i-lkp@xxxxxxxxx/config) > > compiler: aarch64-linux-gcc (GCC) 12.3.0 > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250625/202506252117.9V3HTO0i-lkp@xxxxxxxxx/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@xxxxxxxxx> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202506252117.9V3HTO0i-lkp@xxxxxxxxx/ > > > > All errors (new ones prefixed by >>): > > > > aarch64-linux-ld: fs/fuse/file.o: in function `fuse_writepages': > > >> file.c:(.text+0xa30): undefined reference to `iomap_writepages' > > >> file.c:(.text+0xa30): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `iomap_writepages' > > aarch64-linux-ld: fs/fuse/file.o: in function `fuse_writepage_finish': > > >> file.c:(.text+0x1fd8): undefined reference to `iomap_finish_folio_write' > > >> file.c:(.text+0x1fd8): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `iomap_finish_folio_write' > > aarch64-linux-ld: fs/fuse/file.o: in function `fuse_cache_write_iter': > > file.c:(.text+0x888c): undefined reference to `iomap_file_buffered_write' > > file.c:(.text+0x888c): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `iomap_file_buffered_write' > > aarch64-linux-ld: fs/fuse/file.o: in function `fuse_iomap_writeback_range': > > >> file.c:(.text+0x9258): undefined reference to `iomap_start_folio_write' > > >> file.c:(.text+0x9258): relocation truncated to fit: R_AARCH64_CALL26 against undefined symbol `iomap_start_folio_write' > > >> aarch64-linux-ld: fs/fuse/file.o:(.rodata+0x370): undefined reference to `iomap_dirty_folio' > > aarch64-linux-ld: fs/fuse/file.o:(.rodata+0x3a0): undefined reference to `iomap_release_folio' > > > > -- > > 0-DAY CI Kernel Test Service > > https://github.com/intel/lkp-tests/wiki > > As noted in the cover letter [1] > > Please note the following: > * this patchset version temporarily drops the CONFIG_BLOCK iomap refactoring > patches that will be needed to merge in the series. As of now, this breaks > compilation for environments where CONFIG_BLOCK is not set, but the > CONFIG_BLOCK iomap changes will be re-added back in once the core changes > in this patchset are ready to go. > > > These errors will be fixed in later versions when the CONFIG_BLOCK > patches get added in. Ok, sounds good. Main thing is I can merge it all in one go.
