From: Nathan Chancellor <nathan@kernel.org>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: ERROR: modpost: "__popcountsi2" [fs/bcachefs/bcachefs.ko] undefined!
Date: Thu, 8 Aug 2024 17:39:01 -0700 [thread overview]
Message-ID: <20240809003901.GA3870107@thelio-3990X> (raw)
In-Reply-To: <ZrQ7Vj4hf8Fbxa6j@rli9-mobl>
On Thu, Aug 08, 2024 at 11:28:22AM +0800, Philip Li wrote:
> On Wed, Aug 07, 2024 at 08:36:16AM -0700, Nathan Chancellor wrote:
> > On Wed, Aug 07, 2024 at 04:43:13AM +0800, kernel test robot wrote:
> > > Hi Kent,
> > >
> > > First bad commit (maybe != root cause):
> > >
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > > head: eb5e56d1491297e0881c95824e2050b7c205f0d4
> > > commit: 9ae82fe6ace1b267005758ccfb2347a4a6aa4398 bcachefs: Inline make_bfloat() into __build_ro_aux_tree()
> > > date: 10 months ago
> > > config: arm-randconfig-002-20240805 (https://download.01.org/0day-ci/archive/20240807/202408070432.X6n56VaY-lkp@intel.com/config)
> > > compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 423aec6573df4424f90555468128e17073ddc69e)
> > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240807/202408070432.X6n56VaY-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/202408070432.X6n56VaY-lkp@intel.com/
> > >
> > > All errors (new ones prefixed by >>, old ones prefixed by <<):
> > ...
> > > ERROR: modpost: "__popcountsi2" [fs/ext4/ext4.ko] undefined!
> > > ERROR: modpost: "__popcountsi2" [fs/fat/fat.ko] undefined!
> > > ERROR: modpost: "__popcountsi2" [fs/hfsplus/hfsplus.ko] undefined!
> > > ERROR: modpost: "__popcountsi2" [fs/xfs/xfs.ko] undefined!
> > > ERROR: modpost: "__popcountsi2" [fs/gfs2/gfs2.ko] undefined!
> > > >> ERROR: modpost: "__popcountsi2" [fs/bcachefs/bcachefs.ko] undefined!
> > > ERROR: modpost: "__aeabi_uldivmod" [fs/bcachefs/bcachefs.ko] undefined!
> > > ERROR: modpost: "__popcountsi2" [drivers/block/virtio_blk.ko] undefined!
> > > ERROR: modpost: "__popcountsi2" [drivers/net/ipa/ipa.ko] undefined!
> > > ERROR: modpost: "__popcountsi2" [drivers/memory/emif.ko] undefined!
> > > WARNING: modpost: suppressed 5 unresolved symbol warnings because there were too many)
> >
> > Intel folks, can you upgrade your build of Clang main to
> > https://github.com/llvm/llvm-project/commit/4527fba9ad6bc682eceda603150bfaec65ec6916?
>
> Got it, we will update clang to this version 4527fba9.
Thanks a lot! Is there a way to notice when a compiler upgrade causes a
lot of similar reports to be generated? If so, would it be possible to
send the reports that would be generated to only me and
llvm@lists.linux.dev? We want to get notified when there would be a lot
of reports generated after a compiler upgrade (because that usually
points to a compiler regression) but kernel developers shouldn't get
notified (since there is not anything for them to do).
> > The current revision is broken and unrelated changes are getting
> > notified. There might be one more regression that I am looking into, so
> > consider not going further than that revision.
>
> Ok, we will keep at 4527fba9, and kindly let us know if we can move to
> latest head.
You should be able to move to the latest whenever now, the regression I
noticed was fixed with a revert (it has since been reapplied with a
fix).
Cheers,
Nathan
next prev parent reply other threads:[~2024-08-09 0:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 20:43 kernel test robot
2024-08-07 15:36 ` Nathan Chancellor
2024-08-08 3:28 ` Philip Li
2024-08-09 0:39 ` Nathan Chancellor [this message]
2024-08-09 2:09 ` Philip Li
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=20240809003901.GA3870107@thelio-3990X \
--to=nathan@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=philip.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®