From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Borislav Petkov" <bp@alien8.de>
Subject: Re: WARNING: modpost: "cmpxchg8b_emu" [lib/test_lockup.ko] has no CRC!
Date: Mon, 18 Mar 2024 15:25:22 +0100 [thread overview]
Message-ID: <c9eecda1-a8e2-4ded-89fb-a2cc98d4c19a@app.fastmail.com> (raw)
In-Reply-To: <202403182122.G6VFSE9v-lkp@intel.com>
On Mon, Mar 18, 2024, at 14:27, kernel test robot wrote:
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: f6cef5f8c37f58a3bc95b3754c3ae98e086631ca
> commit: 88a2b4edda3d0709727be53f4423b0b832d91de3 x86/Kconfig: Rework
> CONFIG_X86_PAE dependency
> date: 3 months ago
> config: um-randconfig-r035-20230726
> WARNING: modpost: EXPORT symbol "cmpxchg8b_emu" [vmlinux] version
> generation failed, symbol will not be versioned.
> Is "cmpxchg8b_emu" prototyped in <asm/asm-prototypes.h>?
> WARNING: modpost: EXPORT symbol "csum_partial" [vmlinux] version
> generation failed, symbol will not be versioned.
> Is "csum_partial" prototyped in <asm/asm-prototypes.h>?
> WARNING: modpost: EXPORT symbol "csum_partial_copy_generic" [vmlinux]
> version generation failed, symbol will not be versioned.
> Is "csum_partial_copy_generic" prototyped in <asm/asm-prototypes.h>?
>>> WARNING: modpost: "cmpxchg8b_emu" [lib/test_lockup.ko] has no CRC!
>>> WARNING: modpost: "cmpxchg8b_emu" [lib/atomic64_test.ko] has no CRC!
I have not tested arch/um randconfig builds, but my guess is that
this was not actually introduced by my patch but rather lkp bisected
this into my commit because that changed the config in a way that
hides the preexisting bug on older kernels.
Arnd
prev parent reply other threads:[~2024-03-18 14:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 13:27 WARNING: modpost: "cmpxchg8b_emu" [lib/test_lockup.ko] has no CRC! kernel test robot
2024-03-18 14:25 ` Arnd Bergmann [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=c9eecda1-a8e2-4ded-89fb-a2cc98d4c19a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).