Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp3448076iob; Sat, 7 May 2022 05:32:00 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwQT2Pmui29BJxv4p5drD7eOXJS1ng00FA8H++rNdxwi86U0jUouJF+XFsZXqfHwh7l4Mjl X-Received: by 2002:a05:6808:1b22:b0:326:a5fb:faa5 with SMTP id bx34-20020a0568081b2200b00326a5fbfaa5mr1518679oib.50.1651926719988; Sat, 07 May 2022 05:31:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651926719; cv=none; d=google.com; s=arc-20160816; b=0PGqDDP29Hrlt4Tnklv3b0O1mZyDGdwvN1lRUlqSPwR6lPw9F6dwRsOL4BwPMP9I6w tTY7Mfh67BXAXwbXjm0xmB5lOF362LkzGmqY/Ppg6EhCvZqFXGLc+z4ISt8VG9raV9hO EgUeUGRkwKYyzXzA/vmQoUDi/HBRjA7Aoaxa5AOiXOZ2Inz/3NM44dGDhEkSKd2x0qzc 7YE15sNKZfttdrbw7MlLKm3lzM1HsN0oYUYNNICI87ddP/8oYbAg3/Ly62NlWRQo2D8y biqP45T0HSIKetDMcvbgEbOdHu+8bTsjYpwnY/CUJCbRmnJhDmDxX26t8BA/9tXKPHLU qHzw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=bD37yb+eTq59cJ9djBfKW5Fj/AYgK7FEbCYsEn9P904=; b=GsaHBxe0NomMHQPqOHzauVV69s8SidhjnYsu5ZMbXkknoOFxE9Fx6EVU8j0k8jte7E b9o4IEfgR+/OntQzSpITEkPX7iDVIJs3xLWfbEtUYJTgZ5dX5Ev5p2mb4ox0yS6UlamC q28VQ+l3GZzKWdlCI+EUqDt3GLCFt8W+i544bfplCteSwzGRnXevMg9CE7YZXrNEsTK6 GSMDg8qji07d0GqfTin/OpX4gSVboyubWpDkuDkQS81/sS32SKg/OGLeuHhSiBVbTRE2 SeVMWQ7lEz1RAYwTVc4M+Z73GvUcunSigqmYAjFPRnC7/Sa4UGNVDNd/aordtSN6xd7u 8jMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FNMAdsi+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v5-20020a05687105c500b000ddb3d78e47si4110690oan.77.2022.05.07.05.31.45; Sat, 07 May 2022 05:31:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=FNMAdsi+; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1357620AbiEEQOw (ORCPT + 99 others); Thu, 5 May 2022 12:14:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37560 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1381875AbiEEQOu (ORCPT ); Thu, 5 May 2022 12:14:50 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 599701D30B; Thu, 5 May 2022 09:11:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1651767060; x=1683303060; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=1eGeIh+xMiBRTxqWkXlfYujous1v8oMKzohvreSWsN8=; b=FNMAdsi+bg+d8+nosUfVJUoMrzCP+ZwWMIIQ38Sis9BZBryE1ITu1E24 /F8BHqZsOr/ZDTPD3/safwHP+4+KVD6dds7ponxMCg40eon1sCWXVL/25 MgLPGzhmn4F/GvSULHgWYJsczT5Tn68ITVnCmq9TG4Os63l3rJxWGULVq TqWTOrlj2Pa0QGs7LQUDgdYRrl0hzbogNCb1PQhwlzeDoN5ItvVN+6t4/ Ql8gC/WlZLP03T/ZV2OodXeDhsnXV6P3g0XvSGZUMRTFlXriAQQH6p7tK ObfP/5DoCeyQ3wW46OXSGOvS7iwwOSAM3ZuwhUkRueHfCEKQJJY8iOCeX w==; X-IronPort-AV: E=McAfee;i="6400,9594,10338"; a="331155509" X-IronPort-AV: E=Sophos;i="5.91,201,1647327600"; d="scan'208";a="331155509" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga105.jf.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-Spam-Status: No, score=-5.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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