From: Yujie Liu <yujie.liu@intel.com>
To: Marcos Paulo de Souza <mpdesouza@suse.com>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>,
"Linux Memory Management List" <linux-mm@kvack.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [linux-next:master 10409/11394] ERROR: modpost: "__fentry__" [tools/testing/selftests/livepatch/test_modules/test_klp_atomic_replace.ko] undefined!
Date: Tue, 5 Mar 2024 22:05:46 +0800 [thread overview]
Message-ID: <Zecmuk1OlU7VO8Bk@yujie-X299> (raw)
In-Reply-To: <20240304122921.31671-1-mpdesouza@suse.com>
Hi Marcos,
On Mon, Mar 04, 2024 at 09:29:19AM -0300, Marcos Paulo de Souza wrote:
> On Sat, 2 Mar 2024 14:14:12 +0800 kernel test robot <lkp@intel.com> wrote:
>
> > Hi Marcos,
> >
> > First bad commit (maybe != root cause):
> >
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > head: 1870cdc0e8dee32e3c221704a2977898ba4c10e8
> > commit: 539cd3f4da3fdbe7dc353634e004e4b0e725c35a [10409/11394] selftests: lib.mk: Do not process TEST_GEN_MODS_DIR
> > 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/20240302/202403021440.Rs4qG6fP-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/202403021440.Rs4qG6fP-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.
>
> This seems suspicious. Can you be sure that kernel-devel was installed properly
> in this machine? We have landed a patch to skip building the tests if
> kernel-devel is not installed. We check if /lib/modules/<kernel-version/build
> is present to start building, but I would expect Module.symvers to be present.
>
> Please let me know if we need to adapt our tests further to avoid such problems.
Sorry, this is another problem due to the different way of organizing
the files at the bot side. We are looking into this to put the required
materials to the correct path. This report should be a false positive,
please ignore it.
> > 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/livepatch/test_modules/test_klp_atomic_replace.ko] undefined!
> > >> ERROR: modpost: "klp_enable_patch" [tools/testing/selftests/livepatch/test_modules/test_klp_atomic_replace.ko] undefined!
> > >> ERROR: modpost: "seq_printf" [tools/testing/selftests/livepatch/test_modules/test_klp_atomic_replace.ko] undefined!
> > >> ERROR: modpost: "param_ops_int" [tools/testing/selftests/livepatch/test_modules/test_klp_atomic_replace.ko] undefined!
> > >> ERROR: modpost: "module_layout" [tools/testing/selftests/livepatch/test_modules/test_klp_atomic_replace.ko] undefined!
> > >> ERROR: modpost: "__fentry__" [tools/testing/selftests/livepatch/test_modules/test_klp_callbacks_busy.ko] undefined!
> > >> ERROR: modpost: "flush_work" [tools/testing/selftests/livepatch/test_modules/test_klp_callbacks_busy.ko] undefined!
> > >> ERROR: modpost: "_printk" [tools/testing/selftests/livepatch/test_modules/test_klp_callbacks_busy.ko] undefined!
> > >> ERROR: modpost: "complete" [tools/testing/selftests/livepatch/test_modules/test_klp_callbacks_busy.ko] undefined!
> > >> ERROR: modpost: "msleep" [tools/testing/selftests/livepatch/test_modules/test_klp_callbacks_busy.ko] undefined!
> > WARNING: modpost: suppressed 80 unresolved symbol warnings because there were too many)
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
>
next prev parent reply other threads:[~2024-03-05 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 6:14 kernel test robot
2024-03-04 12:29 ` Marcos Paulo de Souza
2024-03-05 14:05 ` Yujie Liu [this message]
2024-03-07 12:01 ` Marcos Paulo de Souza
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=Zecmuk1OlU7VO8Bk@yujie-X299 \
--to=yujie.liu@intel.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mpdesouza@suse.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=skhan@linuxfoundation.org \
/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