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:iomap-fuse-prep 7/8] fs/iomap/buffered-io.c:2015:undefined reference to `iomap_add_to_ioend'
Date: Wed, 20 May 2026 14:05:44 +0800 [thread overview]
Message-ID: <202605201401.wxEhP1vF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git iomap-fuse-prep
head: d78140ae7e41edad8f0971778c7c21a6f3da650c
commit: 30ec00229eecd235b3b6bc15f6fd20bcf9a3670a [7/8] iomap: map writeback ranges with iomap ops
config: i386-buildonly-randconfig-002-20260520 (https://download.01.org/0day-ci/archive/20260520/202605201401.wxEhP1vF-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260520/202605201401.wxEhP1vF-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/202605201401.wxEhP1vF-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: fs/iomap/buffered-io.o: in function `iomap_writeback_map':
>> fs/iomap/buffered-io.c:2015:(.text+0x298): undefined reference to `iomap_add_to_ioend'
vim +2015 fs/iomap/buffered-io.c
1997
1998 ssize_t iomap_writeback_map(struct iomap_writepage_ctx *wpc,
1999 struct folio *folio, u64 offset, unsigned int len, u64 end_pos,
2000 const struct iomap_ops *ops)
2001 {
2002 struct iomap_iter iter = {
2003 .inode = wpc->inode,
2004 .pos = offset,
2005 .len = len,
2006 .flags = IOMAP_WRITEBACK,
2007 };
2008 ssize_t ret;
2009
2010 while ((ret = iomap_iter(&iter, ops)) > 0)
2011 iter.status = iomap_writeback_map_iter(&iter, wpc);
2012 if (ret < 0 && ret != -ECANCELED)
2013 return ret;
2014
> 2015 return iomap_add_to_ioend(wpc, folio, offset, end_pos, len);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-20 6:08 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=202605201401.wxEhP1vF-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.