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 51834C433F5 for ; Thu, 5 May 2022 16:15:21 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id BDBB76B0078; Thu, 5 May 2022 12:15:20 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B8A4E6B007B; Thu, 5 May 2022 12:15:20 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A2A496B007D; Thu, 5 May 2022 12:15:20 -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 922986B0078 for ; Thu, 5 May 2022 12:15:20 -0400 (EDT) Received: from smtpin12.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 5A6872F719 for ; Thu, 5 May 2022 16:15:20 +0000 (UTC) X-FDA: 79432189200.12.7F43B4C Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by imf29.hostedemail.com (Postfix) with ESMTP id 6CBD21200A1 for ; Thu, 5 May 2022 16:15:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1651767318; x=1683303318; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=1eGeIh+xMiBRTxqWkXlfYujous1v8oMKzohvreSWsN8=; b=Eewjg7I5q05vJ+hEU8R9Vtb8U7btfvOx85sVvnqczGQ8T8AtjMVq0KF6 nmbib1PsLIuuun/coLGT8mjWOPAbheUWoR9SQCTdCtbi3MUm4zIwr7baQ pqjkn4Qe+WsvmYC2fHaWy7JkvMVVffq+Bp5eioimnMIDme9a9MQeUX24f xpBW5A9vUU0f6d37hPi7KIt2JKSumXxqyhF225+rSj3p3/mwA4FNX1Y6V I/Xh1XavSukFnQdjhj86Wt4i0hGR1FUhVtKLkfPC2DFaIC3xJidvpweIF nrNZVXjHchjoQNthmUPc0Mp2DpwIZNPrAyaFAI8EVXndJf2KBr93MusrL g==; X-IronPort-AV: E=McAfee;i="6400,9594,10338"; a="354603133" X-IronPort-AV: E=Sophos;i="5.91,201,1647327600"; d="scan'208";a="354603133" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 May 2022 09:10:45 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,201,1647327600"; d="scan'208";a="665035013" Received: from lkp-server01.sh.intel.com (HELO 5056e131ad90) ([10.239.97.150]) by fmsmga002.fm.intel.com with ESMTP; 05 May 2022 09:10:40 -0700 Received: from kbuild by 5056e131ad90 with local (Exim 4.95) (envelope-from ) id 1nme3s-000CXj-Ac; Thu, 05 May 2022 16:10:40 +0000 Date: Fri, 6 May 2022 00:09:59 +0800 From: kernel test robot To: cgel.zte@gmail.com, akpm@linux-foundation.org, hannes@cmpxchg.org, willy@infradead.org, shy828301@gmail.com Cc: kbuild-all@lists.01.org, mhocko@kernel.org, roman.gushchin@linux.dev, shakeelb@google.com, linmiaohe@huawei.com, william.kucharski@oracle.com, peterx@redhat.com, hughd@google.com, vbabka@suse.cz, songmuchun@bytedance.com, surenb@google.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org, Yang Yang Subject: Re: [PATCH] mm/memcg: support control THP behaviour in cgroup Message-ID: <202205052327.RldmheYL-lkp@intel.com> References: <20220505033814.103256-1-xu.xin16@zte.com.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220505033814.103256-1-xu.xin16@zte.com.cn> X-Rspam-User: X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: 6CBD21200A1 X-Stat-Signature: nr9o8mgu1qq51zbzgsy1i6ytfesbmgxf Authentication-Results: imf29.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=Eewjg7I5; spf=none (imf29.hostedemail.com: domain of lkp@intel.com has no SPF policy when checking 192.55.52.43) smtp.mailfrom=lkp@intel.com; dmarc=pass (policy=none) header.from=intel.com X-HE-Tag: 1651767313-11245 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: Hi, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linux/master] [also build test WARNING on linus/master v5.18-rc5] [cannot apply to hnaz-mm/master] [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] url: https://github.com/intel-lab-lkp/linux/commits/cgel-zte-gmail-com/mm-memcg-support-control-THP-behaviour-in-cgroup/20220505-114028 base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 107c948d1d3e61d10aee9d0f7c3d81bbee9842af config: i386-randconfig-s001 (https://download.01.org/0day-ci/archive/20220505/202205052327.RldmheYL-lkp@intel.com/config) compiler: gcc-11 (Debian 11.2.0-20) 11.2.0 reproduce: # apt-get install sparse # sparse version: v0.6.4-dirty # https://github.com/intel-lab-lkp/linux/commit/f08a35b9798572693a91c6a3d823ed9ae54ef688 git remote add linux-review https://github.com/intel-lab-lkp/linux git fetch --no-tags linux-review cgel-zte-gmail-com/mm-memcg-support-control-THP-behaviour-in-cgroup/20220505-114028 git checkout f08a35b9798572693a91c6a3d823ed9ae54ef688 # save the config file mkdir build_dir && cp config build_dir/.config make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot sparse warnings: (new ones prefixed by >>) mm/huge_memory.c: note: in included file (through include/linux/mm.h): >> include/linux/huge_mm.h:272:43: sparse: sparse: marked inline, but without a definition mm/huge_memory.c: note: in included file: >> include/linux/khugepaged.h:30:36: sparse: sparse: marked inline, but without a definition include/linux/khugepaged.h:31:38: sparse: sparse: marked inline, but without a definition -- mm/memory.c:1024:17: sparse: sparse: context imbalance in 'copy_pte_range' - different lock contexts for basic block mm/memory.c:1752:16: sparse: sparse: context imbalance in '__get_locked_pte' - different lock contexts for basic block mm/memory.c:1800:9: sparse: sparse: context imbalance in 'insert_page' - different lock contexts for basic block mm/memory.c:2302:17: sparse: sparse: context imbalance in 'remap_pte_range' - different lock contexts for basic block mm/memory.c:2558:17: sparse: sparse: context imbalance in 'apply_to_pte_range' - unexpected unlock mm/memory.c:2847:9: sparse: sparse: context imbalance in 'wp_page_copy' - different lock contexts for basic block mm/memory.c:3185:17: sparse: sparse: context imbalance in 'wp_pfn_shared' - unexpected unlock mm/memory.c:3248:19: sparse: sparse: context imbalance in 'do_wp_page' - different lock contexts for basic block mm/memory.c: note: in included file (through include/linux/mm.h): >> include/linux/huge_mm.h:272:43: sparse: sparse: marked inline, but without a definition >> include/linux/huge_mm.h:272:43: sparse: sparse: marked inline, but without a definition -- mm/shmem.c: note: in included file: >> include/linux/khugepaged.h:30:36: sparse: sparse: marked inline, but without a definition include/linux/khugepaged.h:31:38: sparse: sparse: marked inline, but without a definition >> include/linux/khugepaged.h:30:36: sparse: sparse: marked inline, but without a definition include/linux/khugepaged.h:31:38: sparse: sparse: marked inline, but without a definition vim +272 include/linux/huge_mm.h 263 264 static inline struct list_head *page_deferred_list(struct page *page) 265 { 266 /* 267 * Global or memcg deferred list in the second tail pages is 268 * occupied by compound_head. 269 */ 270 return &page[2].deferred_list; 271 } > 272 inline bool __transparent_hugepage_enabled(struct vm_area_struct *vma); 273 -- 0-DAY CI Kernel Test Service https://01.org/lkp