On Sat, Mar 23, 2024 at 07:48:03AM +0800, kernel test robot 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@xxxxxxxxx/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@xxxxxxxxx/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@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202403230731.fved39RH-lkp@xxxxxxxxx/ > > 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) We were supposed to be getting 0day testing for our stuff, and we were at one point, clearly that slipped - who would be interesting in helping build a dashboard for 0day so that we can make sure this isn't happening in the future? I want something so that a maintainer can see at a glance that code's been tested before merging. I've got a dashboard for my own CI that we can adapt. Also, I'm build testing mm-unstable on alpha now and I'm seeing more build errors that I don't think we introduced. I'll see what I can fix...
