From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 46CB6C54ED1 for ; Sat, 28 Jun 2025 07:10:43 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 98B816B0098; Sat, 28 Jun 2025 03:10:42 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 962B76B0099; Sat, 28 Jun 2025 03:10:42 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 8A00C6B009A; Sat, 28 Jun 2025 03:10:42 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 792F56B0098 for ; Sat, 28 Jun 2025 03:10:42 -0400 (EDT) Received: from smtpin05.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 028CA1604D2 for ; Sat, 28 Jun 2025 07:10:41 +0000 (UTC) X-FDA: 83603936724.05.25AF12C Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.15]) by imf03.hostedemail.com (Postfix) with ESMTP id 6140220003 for ; Sat, 28 Jun 2025 07:10:39 +0000 (UTC) Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=aL9kU70h; spf=pass (imf03.hostedemail.com: domain of lkp@intel.com designates 198.175.65.15 as permitted sender) smtp.mailfrom=lkp@intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1751094640; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=ioPUWgscyPWmod5/tzPfoDeL7ip2pIgc/ShXrvy8Bb0=; b=jUms72Cn6mBP4vQyDQLWB4sFdf9MMDDW69BO+AFQZSRIbuReDHqotC/3oa7CUFEExU9btf 8cYExZHyPCw3Jwr3zVl1thjE4vXDwuFQi0Blg0wgQ6nse0Vae9+Vro/DxMIsWQS2r5tPah 6PnXgGsgN7VgGl3YuuznGTHjz7hVjtw= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1751094640; a=rsa-sha256; cv=none; b=bXbBvAwaKFz2qvzTVprsfhwYY9nFKPDHU5/o++gMoTPphJ8Uy5OFiic17+fMwPdXRZF2mG ujwSS9S3mEUnYI4v2yErl8wBz7cBYSRPU3Te7R6tpIEbQIDjKjmVa0ymDRjSLHCRAS7nY1 KL17fPNrTo9Z8XK4tIw41fktxMVt/hs= ARC-Authentication-Results: i=1; imf03.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=aL9kU70h; spf=pass (imf03.hostedemail.com: domain of lkp@intel.com designates 198.175.65.15 as permitted sender) smtp.mailfrom=lkp@intel.com; dmarc=pass (policy=none) header.from=intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1751094639; x=1782630639; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=2tVRa6wsMqTyE/oQPrMRT6Uokojksj6kxjX9glGnRB0=; b=aL9kU70hnzy3lVXA8KWfl4aYpyoXisDKBMZQRY+W1VeAnp/BnzniABuN LvNS3/GE4Nm4YvRcCiGq9bzyRxevZBaHmyFgV3lCfUcxE/4/V/pXrOo9q lBuofDOxN7mRoFvZW8GOoP1PRwIs2iHuLqW7IqXl7XxUqZAMtQj4aFtRi 4aTNVeJw+zZirldB4YO3WNw76mi7VycmtKojfQvDPTJv25djjF4B2G+me cBf26+8fVShGOqPFwqu2kPlQ9+/m1TAD1I1ETB8/U6Ds/NAzLh+OGYSFN hX8myDni8b29m7XPgJ/5kaQTWuh/l+yLioOPVtoIHUdu/tu/zk5mdJgbL Q==; X-CSE-ConnectionGUID: 8mcjLnaVQNilcQcL8iMYFQ== X-CSE-MsgGUID: Cqg1u6RISfm7/HzlhqDK3A== X-IronPort-AV: E=McAfee;i="6800,10657,11477"; a="57080307" X-IronPort-AV: E=Sophos;i="6.16,272,1744095600"; d="scan'208";a="57080307" Received: from fmviesa004.fm.intel.com ([10.60.135.144]) by orvoesa107.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jun 2025 00:10:37 -0700 X-CSE-ConnectionGUID: ohOsf+HWQWOFrhTjoH3+RA== X-CSE-MsgGUID: zP+1cSr+RoWpV9omkLPlxw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,272,1744095600"; d="scan'208";a="158488584" Received: from lkp-server01.sh.intel.com (HELO e8142ee1dce2) ([10.239.97.150]) by fmviesa004.fm.intel.com with ESMTP; 28 Jun 2025 00:10:32 -0700 Received: from kbuild by e8142ee1dce2 with local (Exim 4.96) (envelope-from ) id 1uVPhm-000Wsw-0M; Sat, 28 Jun 2025 07:10:30 +0000 Date: Sat, 28 Jun 2025 15:10:26 +0800 From: kernel test robot To: Jonathan Cameron , Catalin Marinas , james.morse@arm.com, linux-cxl@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-acpi@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, gregkh@linuxfoundation.org, Will Deacon , Dan Williams , Davidlohr Bueso Cc: oe-kbuild-all@lists.linux.dev, Yicong Yang , linuxarm@huawei.com, Yushan Wang , Lorenzo Pieralisi , Mark Rutland , Dave Hansen , Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, H Peter Anvin , Andy Lutomirski , Peter Zijlstra Subject: Re: [PATCH v2 5/8] arm64: Select GENERIC_CPU_CACHE_INVALIDATE_MEMREGION Message-ID: <202506281452.zc1D1sSz-lkp@intel.com> References: <20250624154805.66985-6-Jonathan.Cameron@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250624154805.66985-6-Jonathan.Cameron@huawei.com> X-Rspam-User: X-Rspamd-Server: rspam12 X-Rspamd-Queue-Id: 6140220003 X-Stat-Signature: wusn79tgwz6c5tqz1stbhita7dsjxeoj X-HE-Tag: 1751094639-910602 X-HE-Meta: U2FsdGVkX19Qm/8XejX04tjweq3K1CPGslKeX3VKqfVS3P4IfI2aPBje0wDMoOLeBx4m2RxVw2XEVklaDar1eZNguyqNFud5tLFd4JK3nh0dLzPcAQrWIfGmlnFWR4YnljH5s/Imteryu1+UhB6AGH2b6G/c3JUFSwJd4/ylxoVDEpH5Q36hgIYGrNTxPXmvko0LWAciMFiqoqg2SUZ28UN1RiB9+Y6eW3TdXlO3CxqBxfPJxXcV4+ZC7F/fkWyqWkofOSK7RJZzgODo9gIiMroW1WMBM24LBT94DKh3S6M3kuA3b7i3e0YwOOImOaNwC2UfcE4glUg97no5zVvggZ67hV0f/PCPuYWs2N1CyQIBNoLCaPr3SjszYeABVSLUj3TZYEQrXIX8alaEGgjIjzU64CENWKjSTg4+78nq4ZonloYTulLFo5ZI4aiR/ndqsXVX60XLgHJ+NI1J9QATNDp4a8INi3HrIxX0HyCtB4ebzz5uoRqXeUM1Hb2/lq6onDAHZSkuVnQQAEKBQzFxLBPQhmmxyE1N6GEYh5UtR4K3V/jqmT5VNE1/LZC+tzDRlc/umWdx3VYZ06g7afpv1hR+CityiSJuALu4hpW+0HLPR8Wz4MwnaJTRhmczhVqpHqKZnBmRZBosch2TSGsjKLhb0bM9UBItzfQAdmK1Enbo+1/jr8KkcBbeGkew5cKcArPPSVBnOJnhHioR8KZH/l8G7gWbtrHBtpcQXcvPAWxlS2jLHw5cs2qO2NVh6rEr0npm6ump8g53RoSrzMzTXR4Ng0Cb1L7SPlhnOeisua8wxMnBvCYWGuysDMe4auQ31s6P3ISIsZr0/2Bp4g8TbHLIoTUuctM2S1zYL9afbn97PUppZOXdIXXycXEURQUk7FpnC7nI3Yf0mgl6urIW4yCs6NeJ7Lp82d5q6um+ot5pfOgilqvTnwMYGXlmZmtjcU3jUqG9+F4LI2yKlBU c+TXhvxF ZsvuINLTCgrNjtIp7abI0qpx4oMdWHWBlVlJymqp09IzW6+jDYul+23E027ZoBo8+UFanbNtAR0t5eYVs8ZrqcuL7pbdzeKEwZ1REc0Mse2QaDRSQCnZTNmQ/InMmFKDyEuuMc32+L20ZZmAr3SkevPGxKYhnWS2V5dDa7ZjGawW5xBGAXIMrgJzXbWv7I5XFh570N6BTcEb7KHBxucy7eM7kxQzmrZfibwNUoiHkZajHM7bVmpxfHskRXNPc4Jllx16Pd/mRbo20fsBQ6xgPu36OATD23KtoLXSU8FNJ/vIE64LHPDxCk3aSA632Bk7OrhGSvmvFt714PKYvqFufEwbFE4RKQ+RCk2sAxYsKRp1mccZ9RRT7SRi8WOGKMWB8NFrH+abHxqbkdScYTa9qRR5a5YuOpunjSrDtwaoh0fsBatM= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: Hi Jonathan, kernel test robot noticed the following build warnings: [auto build test WARNING on driver-core/driver-core-testing] [also build test WARNING on driver-core/driver-core-next driver-core/driver-core-linus arm64/for-next/core linus/master nvdimm/libnvdimm-for-next v6.16-rc3] [cannot apply to nvdimm/dax-misc next-20250627] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Jonathan-Cameron/memregion-Support-fine-grained-invalidate-by-cpu_cache_invalidate_memregion/20250624-235402 base: driver-core/driver-core-testing patch link: https://lore.kernel.org/r/20250624154805.66985-6-Jonathan.Cameron%40huawei.com patch subject: [PATCH v2 5/8] arm64: Select GENERIC_CPU_CACHE_INVALIDATE_MEMREGION config: arm64-randconfig-r111-20250628 (https://download.01.org/0day-ci/archive/20250628/202506281452.zc1D1sSz-lkp@intel.com/config) compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project e04c938cc08a90ae60440ce22d072ebc69d67ee8) reproduce: (https://download.01.org/0day-ci/archive/20250628/202506281452.zc1D1sSz-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 | Closes: https://lore.kernel.org/oe-kbuild-all/202506281452.zc1D1sSz-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) >> drivers/base/cache.c:12:1: sparse: sparse: symbol 'scfm_lock' was not declared. Should it be static? drivers/base/cache.c:14:6: sparse: sparse: context imbalance in 'generic_set_sys_cache_flush_method' - wrong count at exit drivers/base/cache.c:27:9: sparse: sparse: context imbalance in 'generic_clr_sys_cache_flush_method' - wrong count at exit drivers/base/cache.c:31:5: sparse: sparse: context imbalance in 'cpu_cache_invalidate_memregion' - wrong count at exit drivers/base/cache.c:41:6: sparse: sparse: context imbalance in 'cpu_cache_has_invalidate_memregion' - wrong count at exit vim +/scfm_lock +12 drivers/base/cache.c b51d47491c68aef Yicong Yang 2025-06-24 9 b51d47491c68aef Yicong Yang 2025-06-24 10 b51d47491c68aef Yicong Yang 2025-06-24 11 static const struct system_cache_flush_method *scfm_data; b51d47491c68aef Yicong Yang 2025-06-24 @12 DEFINE_SPINLOCK(scfm_lock); b51d47491c68aef Yicong Yang 2025-06-24 13 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki