All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Christian Brauner	 <christianvanbrauner@gmail.com>,
	Christian Brauner <brauner@kernel.org>,
	 Christoph Hellwig	 <hch@lst.de>, Jan Kara <jack@suse.cz>,
	Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [brauner-vfs:vfs.all 66/107] ERROR: modpost: "__aeabi_uldivmod" [fs/nilfs2/nilfs2.ko] undefined!
Date: Tue, 10 Mar 2026 07:29:07 -0400	[thread overview]
Message-ID: <441a4f44faf11321df5708ff933c54f8acf2bef9.camel@kernel.org> (raw)
In-Reply-To: <202603100602.KPxiClIO-lkp@intel.com>

On Tue, 2026-03-10 at 06:37 +0800, kernel test robot wrote:
> Hi Jeff,
> 
> 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/vfs/vfs.git vfs.all
> head:   521aad921ebdcd2d87e3862753fe6739ee3b24bc
> commit: 0b2600f81cefcdfcda58d50df7be8fd48ada8ce2 [66/107] treewide: change inode->i_ino from unsigned long to u64
> config: arm-randconfig-004-20260310 (https://download.01.org/0day-ci/archive/20260310/202603100602.KPxiClIO-lkp@intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 8.5.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260310/202603100602.KPxiClIO-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/202603100602.KPxiClIO-lkp@intel.com/
> 
> All errors (new ones prefixed by >>, old ones prefixed by <<):
> 
> > > ERROR: modpost: "__aeabi_uldivmod" [fs/nilfs2/nilfs2.ko] undefined!

This looks like a legit problem. There are some division operations
involving i_ino in NILFS2 that I didn't notice before. I'll spin up a
proposed patch (though I don't have a a good way to test it).

-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2026-03-10 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 22:37 [brauner-vfs:vfs.all 66/107] ERROR: modpost: "__aeabi_uldivmod" [fs/nilfs2/nilfs2.ko] undefined! kernel test robot
2026-03-10 11:29 ` Jeff Layton [this message]

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=441a4f44faf11321df5708ff933c54f8acf2bef9.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=brauner@kernel.org \
    --cc=christianvanbrauner@gmail.com \
    --cc=chuck.lever@oracle.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=lkp@intel.com \
    --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.