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: kernel/bpf/verifier.c:15657:undefined reference to `__umoddi3'
Date: Thu, 01 Oct 2026 15:42:04 +0200	[thread overview]
Message-ID: <202610011511.kp41YMdn-lkp@intel.com> (raw)

:::::: 
:::::: Manual check reason: "low confidence bisect report"
:::::: 

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Eduard Zingerman <eddyz87@gmail.com>
CC: 0day robot <lkp@intel.com>

tree:   https://github.com/intel-lab-lkp/linux/commits/Eduard-Zingerman/bpf-track-may_write-flags-in-liveness/20260926-071959
head:   588faaac20422c91861700e863668674da9cc06f
commit: d4a6f606bf5cbb4d84b533905e932f4a79fe17e3 bpf: representation for intervals with steps
date:   5 days ago
:::::: branch date: 5 days ago
:::::: commit date: 5 days ago
config: i386-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20261001/202610011511.kp41YMdn-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/20261001/202610011511.kp41YMdn-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/202610011511.kp41YMdn-lkp@intel.com/

All errors (new ones prefixed by >>):

   ld: kernel/bpf/verifier.o: in function `scalar_step_lsh':
>> kernel/bpf/verifier.c:15657:(.text+0x14102): undefined reference to `__umoddi3'
   ld: kernel/bpf/verifier.o: in function `scalar_step_mul':
   kernel/bpf/verifier.c:15646:(.text+0x15376): undefined reference to `__umoddi3'


vim +15657 kernel/bpf/verifier.c

d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15650  
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15651  static void scalar_step_lsh(struct bpf_reg_state *dst_reg, struct bpf_reg_state *src_reg)
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15652  {
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15653  	u64 amount = src_reg->var_off.value;
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15654  
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15655  	if (tnum_is_const(src_reg->var_off) && amount < 64 &&
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15656  	    !check_mul_overflow(dst_reg->step, 1ull << amount, &dst_reg->step))
d4a6f606bf5cbb Eduard Zingerman 2026-09-26 @15657  		dst_reg->base = (dst_reg->base * (1ull << amount)) % dst_reg->step;
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15658  	else
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15659  		reg_step_reset(dst_reg);
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15660  }
d4a6f606bf5cbb Eduard Zingerman 2026-09-26  15661  

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

             reply	other threads:[~2026-10-01 13:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 13:42 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-03 14:43 kernel/bpf/verifier.c:15657:undefined reference to `__umoddi3' 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=202610011511.kp41YMdn-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.