From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by gnuweeb.org (Postfix) with ESMTPS id 406017E723 for ; Wed, 30 Mar 2022 06:53:46 +0000 (UTC) Authentication-Results: gnuweeb.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=hBectIj9; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1648623226; x=1680159226; h=date:from:to:cc:subject:message-id:mime-version; bh=cm7zalOPVoseD2/NZNf63+7ZwazgOQ0XcSWIJMqTgps=; b=hBectIj9/HR5JI5GedHbHm1/pKln6vb9Z3MxHfzgKVYS+dsFJ6gz8b1z 9hOCGwFVCT03bBSMV3ezKbUyuMsZyNIyxCv1zpvJoUADxzkFuNsYATMQu 41r5oDex9V2fx5wM9YgHJG4A30IvwxDN3fArg+slPfXGxgkhurnSLv0Yl WGnHGeVf6ZWYzSzvVn7S9fzvpNlyhwudOc7T29edNjW2u1eEBPu5ciMWU udx9ryI8ed5azQfx2EQqj160rUsQzVDMOlpmFRhdGNh+dwVKwrWmgwNgJ xXrwpHEp+zHRobMI7vOSRUQbLvroyZOK97xdb9QLad7Y30+RTeC/iZmm5 w==; X-IronPort-AV: E=McAfee;i="6200,9189,10301"; a="320161302" X-IronPort-AV: E=Sophos;i="5.90,221,1643702400"; d="scan'208";a="320161302" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Mar 2022 23:53:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.90,222,1643702400"; d="scan'208";a="503198264" Received: from lkp-server01.sh.intel.com (HELO 3965e2759b93) ([10.239.97.150]) by orsmga003.jf.intel.com with ESMTP; 29 Mar 2022 23:53:43 -0700 Received: from kbuild by 3965e2759b93 with local (Exim 4.92) (envelope-from ) id 1nZSD8-000150-GS; Wed, 30 Mar 2022 06:53:42 +0000 Date: Wed, 30 Mar 2022 14:53:14 +0800 From: kernel test robot To: Roman Gushchin Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org, GNU/Weeb Mailing List , linux-kernel@vger.kernel.org, Suren Baghdasaryan , Mike Rapoport , Andrew Morton , Linux Memory Management List , Minchan Kim Subject: [ammarfaizi2-block:google/android/kernel/common/android12-trusty-5.10 4036/5872] WARNING: modpost: vmlinux.o(.text+0x4111c4): Section mismatch in reference from the function memblock_bottom_up() to the variable .meminit.data:memblock Message-ID: <202203301412.MZ7wQvQz-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: Hi Roman, FYI, the error/warning still remains. tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android12-trusty-5.10 head: 07055bfd3d810d41a38354693dfaa55a6f8c0025 commit: 0e0bfc41fdf4d79d39ebe929844cdee44f97366d [4036/5872] UPSTREAM: mm: cma: allocate cma areas bottom-up config: x86_64-randconfig-a005 (https://download.01.org/0day-ci/archive/20220330/202203301412.MZ7wQvQz-lkp@intel.com/config) compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 0f6d9501cf49ce02937099350d08f20c4af86f3d) reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # https://github.com/ammarfaizi2/linux-block/commit/0e0bfc41fdf4d79d39ebe929844cdee44f97366d git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android12-trusty-5.10 git checkout 0e0bfc41fdf4d79d39ebe929844cdee44f97366d # save the config file to linux build tree mkdir build_dir COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot All warnings (new ones prefixed by >>, old ones prefixed by <<): >> WARNING: modpost: vmlinux.o(.text+0x4111c4): Section mismatch in reference from the function memblock_bottom_up() to the variable .meminit.data:memblock The function memblock_bottom_up() references the variable __meminitdata memblock. This is often because memblock_bottom_up lacks a __meminitdata annotation or the annotation of memblock is wrong. -- 0-DAY CI Kernel Test Service https://01.org/lkp