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 4442EC7115A for ; Sun, 22 Jun 2025 19:09:39 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id BD3A26B00A4; Sun, 22 Jun 2025 15:09:38 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id BAB626B00A5; Sun, 22 Jun 2025 15:09:38 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A99AE6B00A6; Sun, 22 Jun 2025 15:09:38 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 94A326B00A4 for ; Sun, 22 Jun 2025 15:09:38 -0400 (EDT) Received: from smtpin23.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 64090C0E11 for ; Sun, 22 Jun 2025 19:09:38 +0000 (UTC) X-FDA: 83583975636.23.2D6088B Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.12]) by imf15.hostedemail.com (Postfix) with ESMTP id C69CAA0006 for ; Sun, 22 Jun 2025 19:09:35 +0000 (UTC) Authentication-Results: imf15.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=gMXOo9zd; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf15.hostedemail.com: domain of lkp@intel.com designates 198.175.65.12 as permitted sender) smtp.mailfrom=lkp@intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1750619376; a=rsa-sha256; cv=none; b=43Gtb43fKpylPOm4Txf2fm8ZUkeEk3MrhuztXPXlXuxoBP7oJ2/zn1A1w1oOOqFC72ooio hE7YrgQDEPgEkptKLljMHc/H0MQoD4I6ev+2PWFs0Xn2wocNaNuv7OM05nMC1XsCCFtcxz PeoyZeRVqdl37Ug0OxKKOzA6tapAe48= ARC-Authentication-Results: i=1; imf15.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=gMXOo9zd; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf15.hostedemail.com: domain of lkp@intel.com designates 198.175.65.12 as permitted sender) smtp.mailfrom=lkp@intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1750619376; 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=Cq1qKI8w4DjsLy43sqCCjrFs2UJwGXwgdQgUaWshV1A=; b=zJx3fXa/W4ApLsqXVQQ6TUzg0gAeCEy4IVxYvdvSZOWHLcgD3Y8MTrlJkNq8h3R91HhOSf OLbgBRgwkPrHqQ/hXff8JKVCuFagCxphoPgXIaS0nTKH5JGob54JEJkYcclDdrALmg4cIP dQsMCjUbQU82ef0MgdVIWB7Dq6Fw9+o= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1750619376; x=1782155376; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=sUG1g5y009+hlcy6q+fqDM2WQihyuJLzcTutQ8A27q4=; b=gMXOo9zdyArWLGX5c0K1WBbmjYnAo8BWcLa0TdsUZ6/LjAamT9vbLt1O 2rgjZHSsQh0W42FFFD6wwuxgz3VPUuF1cpBMQODsaRsFptZY4La5xr17c lnhubeYs6NPk6oc1OwXzDn6SxtlfJuIoFaA1kuyPVfxE6j8MDt8eb5YVv FVURS9TFywrAIwKw2mOImFxLjDroqBiD2xHVk9u17ivmxAVANn63FYXcr HMYdaFVHobcTBx0OJQQzhmwzF2yiRxfIMvV2kj/CE3ugQfZjRYf0BZ82f J1PdF12HaaL5fFL43J5MUzToE9LF4+p7roPwmtLzcuK2QJQcSqIx1v3jk w==; X-CSE-ConnectionGUID: rtpGZonBTjafMABOmDXqBA== X-CSE-MsgGUID: DxIIj7qASje4FeMDc/R+FQ== X-IronPort-AV: E=McAfee;i="6800,10657,11472"; a="64257530" X-IronPort-AV: E=Sophos;i="6.16,257,1744095600"; d="scan'208";a="64257530" Received: from fmviesa010.fm.intel.com ([10.60.135.150]) by orvoesa104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jun 2025 12:09:34 -0700 X-CSE-ConnectionGUID: xoACvhAwSguaIkGtPhFf6w== X-CSE-MsgGUID: txG0/ZMaTT+XfePD1hC39g== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,257,1744095600"; d="scan'208";a="152072696" Received: from lkp-server01.sh.intel.com (HELO e8142ee1dce2) ([10.239.97.150]) by fmviesa010.fm.intel.com with ESMTP; 22 Jun 2025 12:09:29 -0700 Received: from kbuild by e8142ee1dce2 with local (Exim 4.96) (envelope-from ) id 1uTQ4F-000NTi-1l; Sun, 22 Jun 2025 19:09:27 +0000 Date: Mon, 23 Jun 2025 03:09:13 +0800 From: kernel test robot To: Peter Xu , linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: oe-kbuild-all@lists.linux.dev, Nikita Kalyazin , peterx@redhat.com, Hugh Dickins , Oscar Salvador , Michal Hocko , David Hildenbrand , Muchun Song , Andrea Arcangeli , Ujwal Kundur , Suren Baghdasaryan , Andrew Morton , Linux Memory Management List , Vlastimil Babka , "Liam R . Howlett" , James Houghton , Mike Rapoport , Lorenzo Stoakes , Axel Rasmussen Subject: Re: [PATCH 4/4] mm: Apply vm_uffd_ops API to core mm Message-ID: <202506230216.JVgQj2Si-lkp@intel.com> References: <20250620190342.1780170-5-peterx@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250620190342.1780170-5-peterx@redhat.com> X-Rspam-User: X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: C69CAA0006 X-Stat-Signature: fkfmywkodqnm4yapnni5uma54nkbn3m7 X-HE-Tag: 1750619375-214352 X-HE-Meta: U2FsdGVkX1+RmNYUqwoFdzK4j+XD68se8aPd+Xg0X2BA/Q4SFE2dwSt+saFnzN3SgB4qxcdivtd1LoZe0iC28IZBYmNOetCeF1CipC4gfuPALp1cdqdyVsPSasriOgoIbe8OOM2haGVARp7Nit+n5tgPglbLbjmk5KEPBxqWni/kRDCLPksZ/i0No+Ct/kY0Dmqx3hK83p0KBUzxyHo78AhZ8AlQSCQjivwwIceJ9e11NOh8GMycpkD2Tar2K7vmy0Sj+ZhHxkbrx3ue5Ju7ImfFmP5cbsq/nj6yQQsS8JxGT2Go3A1PcU4rVuM/33KmgZ+i+zybATO8mdkXRziGZt/1hFxSvlupv5p8eg3B9lx4HvRqFY7r6zQ8XEtOFlOuO36gr3hmOJezlQEk+6thWnz7MyJsKbAXiEkamaLFdj9kw6IE5g5goFHt7VV34YMiXRGNCEjgjyLeU8YXC/UX48VlVtu148CfnTu3nl2SbRqQrxnoFFj5JsxtDX2K49Tz6O5MQGhEIL7DNrGndf/J+pK5HMDJ8DiW2vr8891s0wjI/sh818R4Lc4zM6gxcfOWve5A1yU9GXk37Hw1ubtujc77dtDWQvQdfYt8s+J0Qym67F+bvYDlu9cCH9bG2xL0gzfrOrT95lBoC3m26FWtSkYlAZuMLninVXEo0QfBEbsTb2uukH/KZKgMcwJGCF56KbcqOeTYbDoZuLOMYnI4X17fCVznKYKw5tM5Zms0AfS+SPsBF32XW5peFn7MFGaE816vYmyOjs+f3V5cL9tA8ygp0yMjk7MCPNkqZazNEw/hqO1jFh5q4vz4vjQwTfnT91ZDENKEwYMf83Knd8KpS6RPXJqm4WgQb0XFkz2BB7LxuaW2qWXHWzJqCCH+KVI9W6ouu/f6ZoEmBq3Rbh3iP9uFQ35eJRyr2r+2hw8yK4sbG0ig+GGomkbPz2OUX3aD3SXkt3vxR/sfCe1Whcv KjJhq/by z5qedoUHlAfLRvWMrEkzLt8bA46WKPPKXOaktZLDIfLqiR8RaI1WxAp/gfLkMDbqJEtIxxPH67dAfxzAQC3PWg5DzNwtB3+Bp5kygWaDPidk6DA1Aa4UBOlmWaG/3Mahftk7A8s9t21yohSBfBp41uacPxTn/5gVsuE1m1PaLBemgLMuXbrUqQlaEV88LnMFKuZLM1TAbsHqRImbHfovLK+41cExiIngkReRh+6ObEvcCRpW5zlwU6Dl5Ykg8/S3iJQgRChXmrnSaxEa0PPYmqyXbv2FtjS66joLQCS8CSrzNP8Lf6KzZAdT+62w8W4wkKuMP+hQrglb0gFL10S3+f74mbdbFSqO413cdn47S0jVoBEL4PDSp+atFLeoqwIP2aremOImxB69riCyD9QAvDxZSO+KOzI4yD8PYjpTFlwtFF3KT6kumd5wdNxy89/tE22X9iPiAeaXrZ0bre71en3wh+nH7EHPNXHkhtgJTWNt9XkQzVoWUWqNxJw== 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 Peter, kernel test robot noticed the following build warnings: [auto build test WARNING on next-20250620] [cannot apply to akpm-mm/mm-everything linus/master v6.16-rc2 v6.16-rc1 v6.15 v6.16-rc2] [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/Peter-Xu/mm-Introduce-vm_uffd_ops-API/20250621-030557 base: next-20250620 patch link: https://lore.kernel.org/r/20250620190342.1780170-5-peterx%40redhat.com patch subject: [PATCH 4/4] mm: Apply vm_uffd_ops API to core mm config: i386-randconfig-061-20250622 (https://download.01.org/0day-ci/archive/20250623/202506230216.JVgQj2Si-lkp@intel.com/config) compiler: gcc-11 (Debian 11.3.0-12) 11.3.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250623/202506230216.JVgQj2Si-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/202506230216.JVgQj2Si-lkp@intel.com/ sparse warnings: (new ones prefixed by >>) mm/shmem.c: note: in included file (through include/linux/shmem_fs.h): >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t -- mm/hugetlb.c:669:12: sparse: sparse: context imbalance in 'allocate_file_region_entries' - wrong count at exit mm/hugetlb.c:740:13: sparse: sparse: context imbalance in 'region_add' - wrong count at exit mm/hugetlb.c:807:13: sparse: sparse: context imbalance in 'region_chg' - wrong count at exit mm/hugetlb.c:5798:20: sparse: sparse: context imbalance in 'move_huge_pte' - different lock contexts for basic block mm/hugetlb.c: note: in included file: include/linux/mm.h:1391:22: sparse: sparse: context imbalance in 'hugetlb_wp' - unexpected unlock mm/hugetlb.c: note: in included file (through include/linux/hugetlb.h, include/linux/migrate.h): >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t -- mm/userfaultfd.c:270:9: sparse: sparse: context imbalance in 'mfill_atomic_install_pte' - different lock contexts for basic block mm/userfaultfd.c:412:9: sparse: sparse: context imbalance in 'mfill_atomic_pte_zeropage' - different lock contexts for basic block mm/userfaultfd.c:498:9: sparse: sparse: context imbalance in 'mfill_atomic_pte_poison' - different lock contexts for basic block mm/userfaultfd.c: note: in included file: >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t >> include/linux/userfaultfd_k.h:90:17: sparse: sparse: cast from restricted uffd_flags_t mm/userfaultfd.c: note: in included file (through include/linux/rbtree.h, include/linux/mm_types.h, include/linux/mmzone.h, ...): include/linux/rcupdate.h:871:25: sparse: sparse: context imbalance in 'move_pages_pte' - unexpected unlock vim +90 include/linux/userfaultfd_k.h 87 88 static inline enum mfill_atomic_mode uffd_flags_get_mode(uffd_flags_t flags) 89 { > 90 return (enum mfill_atomic_mode)(flags & MFILL_ATOMIC_MODE_MASK); 91 } 92 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki