All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Paul Moore <paul@paul-moore.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [linux-next:master 1893/5916] .tmp_gl_selinuxfs.o:undefined reference to `__udivdi3'
Date: Sat, 12 Sep 2026 07:11:38 +0800	[thread overview]
Message-ID: <202609120612.r9YCYjLK-lkp@intel.com> (raw)

Hi Paul,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   c68a982815dcce5464e3bf2a31ac94f5146c04ca
commit: fc68b6a45f1668bbe03264343115d1c97013c7ea [1893/5916] selinux: convert selinuxfs inode numbers from unsigned long to u64
config: microblaze-allyesconfig (https://download.01.org/0day-ci/archive/20260912/202609120612.r9YCYjLK-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260912/202609120612.r9YCYjLK-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/202609120612.r9YCYjLK-lkp@intel.com/

All errors (new ones prefixed by >>):

   microblaze-linux-ld: security/selinux/selinuxfs.o: in function `sel_read_class':
>> .tmp_gl_selinuxfs.o:(.text+0x910): undefined reference to `__udivdi3'
   microblaze-linux-ld: security/selinux/selinuxfs.o: in function `sel_read_perm':
>> .tmp_gl_selinuxfs.o:(.text+0x9d0): undefined reference to `__umoddi3'

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

                 reply	other threads:[~2026-09-11 23:12 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=202609120612.r9YCYjLK-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=paul@paul-moore.com \
    /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.