All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Joe Thornber <ejt@redhat.com>
Cc: dm-devel@redhat.com, Mike Snitzer <snitzer@kernel.org>,
	oe-kbuild-all@lists.linux.dev
Subject: [dm-devel] [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:373: undefined reference to `__udivdi3'
Date: Sat, 16 Sep 2023 03:49:53 +0800	[thread overview]
Message-ID: <202309160312.k1ou4uxF-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
head:   785f3bb19d40050d0f40c07cbe6345e361acdcae
commit: b97bcee4b9999c9f5aadc06317ade18c5cbe37f6 [2/4] dm persistent data: Introduce extent allocator
config: i386-randconfig-013-20230915 (https://download.01.org/0day-ci/archive/20230916/202309160312.k1ou4uxF-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/20230916/202309160312.k1ou4uxF-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/202309160312.k1ou4uxF-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: drivers/md/persistent-data/dm-extent-allocator.o: in function `__select_child':
>> drivers/md/persistent-data/dm-extent-allocator.c:373: undefined reference to `__udivdi3'
>> ld: drivers/md/persistent-data/dm-extent-allocator.c:374: undefined reference to `__udivdi3'
>> ld: drivers/md/persistent-data/dm-extent-allocator.c:374: undefined reference to `__udivdi3'
>> ld: drivers/md/persistent-data/dm-extent-allocator.c:373: undefined reference to `__udivdi3'


vim +373 drivers/md/persistent-data/dm-extent-allocator.c

   359	
   360	/**
   361	 * __select_child - Selects the best child node to allocate from in the extent allocator.
   362	 * @ea: Pointer to the extent allocator.
   363	 * @left: left child node.
   364	 * @right: right child node.
   365	 *
   366	 * The best child is the one with the highest ratio of free blocks to holders. If the
   367	 * ratios are equal, the left child is preferred.
   368	 */
   369	static struct node **__select_child(struct dm_extent_allocator *ea, struct node **left, struct node **right)
   370	{
   371		uint64_t left_score, right_score;
   372	
 > 373		left_score = __nr_free_blocks(*left) / ((*left)->nr_holders + 1);
 > 374		right_score = __nr_free_blocks(*right) / ((*right)->nr_holders + 1);
   375	
   376		if (left_score >= right_score)
   377			return left;
   378		else
   379			return right;
   380	}
   381	

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

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Joe Thornber <ejt@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, dm-devel@redhat.com,
	Mike Snitzer <snitzer@kernel.org>
Subject: [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:373: undefined reference to `__udivdi3'
Date: Sat, 16 Sep 2023 03:49:53 +0800	[thread overview]
Message-ID: <202309160312.k1ou4uxF-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git for-next
head:   785f3bb19d40050d0f40c07cbe6345e361acdcae
commit: b97bcee4b9999c9f5aadc06317ade18c5cbe37f6 [2/4] dm persistent data: Introduce extent allocator
config: i386-randconfig-013-20230915 (https://download.01.org/0day-ci/archive/20230916/202309160312.k1ou4uxF-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/20230916/202309160312.k1ou4uxF-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/202309160312.k1ou4uxF-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: drivers/md/persistent-data/dm-extent-allocator.o: in function `__select_child':
>> drivers/md/persistent-data/dm-extent-allocator.c:373: undefined reference to `__udivdi3'
>> ld: drivers/md/persistent-data/dm-extent-allocator.c:374: undefined reference to `__udivdi3'
>> ld: drivers/md/persistent-data/dm-extent-allocator.c:374: undefined reference to `__udivdi3'
>> ld: drivers/md/persistent-data/dm-extent-allocator.c:373: undefined reference to `__udivdi3'


vim +373 drivers/md/persistent-data/dm-extent-allocator.c

   359	
   360	/**
   361	 * __select_child - Selects the best child node to allocate from in the extent allocator.
   362	 * @ea: Pointer to the extent allocator.
   363	 * @left: left child node.
   364	 * @right: right child node.
   365	 *
   366	 * The best child is the one with the highest ratio of free blocks to holders. If the
   367	 * ratios are equal, the left child is preferred.
   368	 */
   369	static struct node **__select_child(struct dm_extent_allocator *ea, struct node **left, struct node **right)
   370	{
   371		uint64_t left_score, right_score;
   372	
 > 373		left_score = __nr_free_blocks(*left) / ((*left)->nr_holders + 1);
 > 374		right_score = __nr_free_blocks(*right) / ((*right)->nr_holders + 1);
   375	
   376		if (left_score >= right_score)
   377			return left;
   378		else
   379			return right;
   380	}
   381	

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

             reply	other threads:[~2023-09-15 19:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 19:49 kernel test robot [this message]
2023-09-15 19:49 ` [device-mapper-dm:for-next 2/4] drivers/md/persistent-data/dm-extent-allocator.c:373: undefined reference to `__udivdi3' 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=202309160312.k1ou4uxF-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dm-devel@redhat.com \
    --cc=ejt@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=snitzer@kernel.org \
    /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.