All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [hch-xfs:xfs-zoned 62/64] fs/xfs/xfs_aops.c:200: undefined reference to `xfs_mark_rtg_boundary'
Date: Tue, 12 Nov 2024 21:28:01 +0800	[thread overview]
Message-ID: <202411122110.ct0FS0fR-lkp@intel.com> (raw)

tree:   git://git.infradead.org/users/hch/xfs xfs-zoned
head:   f9bf4d561e545fe8e988fb807cc47d879f0a00f8
commit: 2469717386951415b1e900370e25b0cc3c8d6b1d [62/64] xfs: use xfs_mark_rtg_boundary in xfs_end_bio
config: x86_64-randconfig-016-20241112 (https://download.01.org/0day-ci/archive/20241112/202411122110.ct0FS0fR-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241112/202411122110.ct0FS0fR-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/202411122110.ct0FS0fR-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: vmlinux.o: in function `xfs_end_bio':
>> fs/xfs/xfs_aops.c:200: undefined reference to `xfs_mark_rtg_boundary'


vim +200 fs/xfs/xfs_aops.c

   184	
   185	void
   186	xfs_end_bio(
   187		struct bio		*bio)
   188	{
   189		struct iomap_ioend	*ioend = iomap_ioend_from_bio(bio);
   190		struct xfs_inode	*ip = XFS_I(ioend->io_inode);
   191		struct xfs_mount	*mp = ip->i_mount;
   192		unsigned long		flags;
   193	
   194		/*
   195		 * For Appends record the actually written block number and set the
   196		 * boundary flag if needed.
   197		 */
   198		if (bio_is_zone_append(bio)) {
   199			ioend->io_sector = bio->bi_iter.bi_sector;
 > 200			xfs_mark_rtg_boundary(ioend);
   201		}
   202	
   203		spin_lock_irqsave(&ip->i_ioend_lock, flags);
   204		if (list_empty(&ip->i_ioend_list))
   205			WARN_ON_ONCE(!queue_work(mp->m_unwritten_workqueue,
   206						 &ip->i_ioend_work));
   207		list_add_tail(&ioend->io_list, &ip->i_ioend_list);
   208		spin_unlock_irqrestore(&ip->i_ioend_lock, flags);
   209	}
   210	

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

             reply	other threads:[~2024-11-12 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 13:28 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-12  0:34 [hch-xfs:xfs-zoned 62/64] fs/xfs/xfs_aops.c:200:undefined reference to `xfs_mark_rtg_boundary' kernel test robot

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=202411122110.ct0FS0fR-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hch@lst.de \
    --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.