From: Suren Baghdasaryan <surenb@google.com>
To: kernel test robot <lkp@intel.com>
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>
Subject: Re: [akpm-mm:mm-unstable 55/141] ERROR: modpost: "memcpy" [fs/nfs/nfs.ko] undefined!
Date: Tue, 26 Mar 2024 00:47:43 -0700 [thread overview]
Message-ID: <CAJuCfpFckAn7HycWma7KTn-MzzMxwcT5s-_SoOz7wFKLs9HLCA@mail.gmail.com> (raw)
In-Reply-To: <202403230731.fved39RH-lkp@intel.com>
On Fri, Mar 22, 2024 at 4:48 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
> head: af520f81c51001f7ccdf0579fc73df282b26292d
> commit: fa5bfe65d50ae7006d711f490bba3cb4d437bcad [55/141] fix missing vmalloc.h includes
> config: alpha-defconfig (https://download.01.org/0day-ci/archive/20240323/202403230731.fved39RH-lkp@intel.com/config)
> compiler: alpha-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240323/202403230731.fved39RH-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/202403230731.fved39RH-lkp@intel.com/
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
> WARNING: modpost: missing MODULE_DESCRIPTION() in vmlinux.o
> WARNING: modpost: "saved_config" [vmlinux] is COMMON symbol
> WARNING: modpost: missing MODULE_DESCRIPTION() in fs/nfs_common/grace.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in fs/nfs/nfs.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in fs/nfs/nfsv2.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in fs/nfs/nfsv3.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/block/loop.o
> ERROR: modpost: "memcpy" [fs/reiserfs/reiserfs.ko] undefined!
> >> ERROR: modpost: "memcpy" [fs/nfs/nfs.ko] undefined!
> >> ERROR: modpost: "memcpy" [fs/nfs/nfsv3.ko] undefined!
> >> ERROR: modpost: "memcpy" [fs/nfsd/nfsd.ko] undefined!
> >> ERROR: modpost: "memcpy" [fs/lockd/lockd.ko] undefined!
> >> ERROR: modpost: "memcpy" [crypto/seqiv.ko] undefined!
> >> ERROR: modpost: "memcpy" [crypto/crypto_null.ko] undefined!
> >> ERROR: modpost: "memcpy" [crypto/sha512_generic.ko] undefined!
> >> ERROR: modpost: "memcpy" [crypto/sha3_generic.ko] undefined!
> >> ERROR: modpost: "memcpy" [crypto/cbc.ko] undefined!
> WARNING: modpost: suppressed 16 unresolved symbol warnings because there were too many)
This and the error reported at
https://lore.kernel.org/all/202403252127.967BczRr-lkp@intel.com/ are
the same. I have a fix but I'm still trying to figure out why this
issue is happening (see
https://lore.kernel.org/all/CAJuCfpH6N_p-w2DxJ530txgTha6dTxQb3ANtkU-6h9pCpstTOA@mail.gmail.com/).
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-03-26 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 23:48 kernel test robot
2024-03-23 0:12 ` Kent Overstreet
2024-03-26 7:47 ` Suren Baghdasaryan [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=CAJuCfpFckAn7HycWma7KTn-MzzMxwcT5s-_SoOz7wFKLs9HLCA@mail.gmail.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pasha.tatashin@soleen.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