From: Nathan Chancellor <nathan@kernel.org>
To: "Chen, Rong A" <rong.a.chen@intel.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
kernel test robot <lkp@intel.com>,
clang-built-linux <llvm@lists.linux.dev>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [kbuild-all] Re: [linux-next:master 6296/7172] ERROR: modpost: "kvm_spurious_fault" [arch/x86/kvm/kvm-intel.ko] undefined!
Date: Fri, 16 Sep 2022 12:00:52 -0700 [thread overview]
Message-ID: <YyTH5NpFvgGahlZk@dev-arch.thelio-3990X> (raw)
In-Reply-To: <97021145-ea61-197c-919e-4a3d606547cf@intel.com>
On Fri, Sep 16, 2022 at 02:37:23PM +0800, Chen, Rong A wrote:
>
>
> On 9/15/2022 11:39 AM, Masahiro Yamada wrote:
> > On Thu, Sep 15, 2022 at 10:37 AM kernel test robot <lkp@intel.com> wrote:
> > >
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > > head: f117c01187301a087412bd6697fcf5463cb427d8
> > > commit: 6676e2cdd7c339dc40331faccbaac1112d2c1d78 [6296/7172] kbuild: use obj-y instead extra-y for objects placed at the head
> > > config: i386-randconfig-a002 (https://download.01.org/0day-ci/archive/20220915/202209150959.hEWCNjXH-lkp@intel.com/config)
> > > compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
> > > reproduce (this is a W=1 build):
> > > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> > > chmod +x ~/bin/make.cross
> > > # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6676e2cdd7c339dc40331faccbaac1112d2c1d78
> > > git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > > git fetch --no-tags linux-next master
> > > git checkout 6676e2cdd7c339dc40331faccbaac1112d2c1d78
> > > # save the config file
> > > mkdir build_dir && cp config build_dir/.config
> > > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
> > >
> > > If you fix the issue, kindly add following tag where applicable
> > > Reported-by: kernel test robot <lkp@intel.com>
> > >
> > > All errors (new ones prefixed by >>, old ones prefixed by <<):
> > >
> > > > > ERROR: modpost: "kvm_spurious_fault" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "___ratelimit" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "_printk" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "__warn_printk" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "kvm_find_user_return_msr" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "__ubsan_handle_out_of_bounds" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "smp_call_function_single" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "cpu_number" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "__per_cpu_offset" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > > > ERROR: modpost: "__phys_addr" [arch/x86/kvm/kvm-intel.ko] undefined!
> > > WARNING: modpost: suppressed 34935 unresolved symbol warnings because there were too many)
> >
> >
> >
> >
> >
> > Sorry, I cannot reproduce this.
> > Seeing the full log might be helpful.
>
> Hi Masahiro,
>
> Sorry for the inconvenience, the error can be found with clang-14,
> but no error with clang-15, it shouldn't be a kernel issue.
We do still want the kernel to build with clang-14 though so this will
require some further investigation. I probably won't be able to get to
it today but I can try to double back on Monday to see what is going on
here unless Masahiro beats me to it.
Cheers,
Nathan
next prev parent reply other threads:[~2022-09-16 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 1:36 kernel test robot
2022-09-15 3:39 ` Masahiro Yamada
2022-09-16 6:37 ` [kbuild-all] " Chen, Rong A
2022-09-16 19:00 ` Nathan Chancellor [this message]
2022-09-19 21:46 ` Nathan Chancellor
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=YyTH5NpFvgGahlZk@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=rong.a.chen@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