From: Philip Li <philip.li@intel.com>
To: Thinker Li <thinker.li@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>,
Martin KaFai Lau <martin.lau@kernel.org>, <sinquersw@gmail.com>
Subject: Re: [linux-next:master 8264/11963] ERROR: modpost: "__fentry__" [tools/testing/selftests/bpf/bpf_test_no_cfi/bpf_test_no_cfi.ko] undefined!
Date: Thu, 7 Mar 2024 09:59:04 +0800 [thread overview]
Message-ID: <ZekfaPDRU+ecVSXJ@rli9-mobl> (raw)
In-Reply-To: <CAFVMQ6ThBWmoSEz==zVH_MvXq+=yvxO5XZJSLUUqJV+kVeULuw@mail.gmail.com>
On Wed, Mar 06, 2024 at 05:55:58PM -0800, Thinker Li wrote:
> I am checking!
Sorry, kindly ignore this report, it is a false positive. And we are working
on resolving the bug in the bot.
>
>
>
> On Tue, Mar 5, 2024 at 9:25 PM kernel test robot <lkp@intel.com> wrote:
> >
> > Hi Kui-Feng,
> >
> > First bad commit (maybe != root cause):
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 11afac187274a6177a7ac82997f8691c0f469e41
> > commit: e9bbda13a7b876451285ab15fb600b809e5e2290 [8264/11963] selftests/bpf: Test case for lacking CFI stub functions.
> > compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240306/202403061307.f7nX2Ma5-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/202403061307.f7nX2Ma5-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>, old ones prefixed by <<):
> >
> > WARNING: Module.symvers is missing.
> > Modules may not have dependencies or modversions.
> > You may get many unresolved symbol errors.
> > You can set KBUILD_MODPOST_WARN=1 to turn errors into warning
> > if you want to proceed at your own risk.
> > >> ERROR: modpost: "__fentry__" [tools/testing/selftests/bpf/bpf_test_no_cfi/bpf_test_no_cfi.ko] undefined!
> > >> ERROR: modpost: "__register_bpf_struct_ops" [tools/testing/selftests/bpf/bpf_test_no_cfi/bpf_test_no_cfi.ko] undefined!
> > >> ERROR: modpost: "module_layout" [tools/testing/selftests/bpf/bpf_test_no_cfi/bpf_test_no_cfi.ko] undefined!
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
>
next prev parent reply other threads:[~2024-03-07 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 5:24 kernel test robot
2024-03-07 1:55 ` Thinker Li
2024-03-07 1:59 ` Philip Li [this message]
2024-03-07 2:08 ` Kui-Feng Lee
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=ZekfaPDRU+ecVSXJ@rli9-mobl \
--to=philip.li@intel.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=martin.lau@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sinquersw@gmail.com \
--cc=thinker.li@gmail.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