All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [jpirko-mlxsw:wip_attestation_all_2 48/68] lib/ctlv/tests/metadata_kunit.c:464:undefined reference to `__umoddi3'
Date: Sat, 14 Nov 2026 15:02:21 +0100	[thread overview]
Message-ID: <202611141437.JLdOOmtq-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "too many reports for this commit | /zdci/kbuild/indicators/3e/3e5d2a45aaa3688da1de5a2430c2993c39451793-reported_build_error_fbc-error"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Jiri Pirko <jiri@nvidia.com>

tree:   https://github.com/jpirko/linux_mlxsw wip_attestation_all_2
head:   7ff5e548abbc2312431d4eea9ad283347963a6e2
commit: 3e5d2a45aaa3688da1de5a2430c2993c39451793 [48/68] ctlv: Add KUnit tests
:::::: branch date: 23 hours ago
:::::: commit date: 23 hours ago
config: xtensa-randconfig-r2302-20261113 (https://download.01.org/0day-ci/archive/20261114/202611141437.JLdOOmtq-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 13.5.0
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261114/202611141437.JLdOOmtq-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/r/202611141437.JLdOOmtq-lkp@intel.com/

All errors (new ones prefixed by >>):

   xtensa-linux-ld: lib/ctlv/tests/metadata_kunit.o: in function `ctlv_meta_test_unlimited':
>> lib/ctlv/tests/metadata_kunit.c:464:(.text+0x958): undefined reference to `__umoddi3'
   xtensa-linux-ld: lib/ctlv/tests/metadata_kunit.o: in function `ctlv_meta_test_assert_constraints':
   lib/ctlv/tests/metadata_kunit.c:385:(.text+0x10f4): undefined reference to `__umoddi3'


vim +464 lib/ctlv/tests/metadata_kunit.c

3e5d2a45aaa368 Jiri Pirko 2026-08-26  448  
3e5d2a45aaa368 Jiri Pirko 2026-08-26  449  static void ctlv_meta_test_unlimited(struct kunit *test)
3e5d2a45aaa368 Jiri Pirko 2026-08-26  450  {
3e5d2a45aaa368 Jiri Pirko 2026-08-26  451  	const struct ctlv_meta_test_case *entry = test->param_value;
3e5d2a45aaa368 Jiri Pirko 2026-08-26  452  	const struct ctlv_family_schema *schema = entry->family->schema;
3e5d2a45aaa368 Jiri Pirko 2026-08-26  453  	u32 i;
3e5d2a45aaa368 Jiri Pirko 2026-08-26  454  
3e5d2a45aaa368 Jiri Pirko 2026-08-26  455  	/* Only a query reply, which may fragment, may be unbounded. */
3e5d2a45aaa368 Jiri Pirko 2026-08-26  456  	for (i = 0; i < schema->ops_count; i++) {
3e5d2a45aaa368 Jiri Pirko 2026-08-26  457  		const struct ctlv_op_schema *op = &schema->ops[i];
3e5d2a45aaa368 Jiri Pirko 2026-08-26  458  
3e5d2a45aaa368 Jiri Pirko 2026-08-26  459  		KUNIT_EXPECT_FALSE(test, ctlv_meta_test_tree_has_unlimited(&op->request));
3e5d2a45aaa368 Jiri Pirko 2026-08-26  460  		if (op->type != CTLV_OP_TYPE_QUERY && op->reply.node_schemas)
3e5d2a45aaa368 Jiri Pirko 2026-08-26  461  			KUNIT_EXPECT_FALSE(test,
3e5d2a45aaa368 Jiri Pirko 2026-08-26  462  					   ctlv_meta_test_tree_has_unlimited(&op->reply));
3e5d2a45aaa368 Jiri Pirko 2026-08-26  463  	}
3e5d2a45aaa368 Jiri Pirko 2026-08-26 @464  }
3e5d2a45aaa368 Jiri Pirko 2026-08-26  465  

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

                 reply	other threads:[~2026-11-14 14:02 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=202611141437.JLdOOmtq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild@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.