From: kernel test robot <lkp@intel.com>
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 <yang.yang29@zte.com.cn>
Subject: Re: [PATCH] mm/memcg: support control THP behaviour in cgroup
Date: Fri, 6 May 2022 00:09:59 +0800 [thread overview]
Message-ID: <202205052327.RldmheYL-lkp@intel.com> (raw)
In-Reply-To: <20220505033814.103256-1-xu.xin16@zte.com.cn>
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 <lkp@intel.com>
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
next prev parent reply other threads:[~2022-05-05 16:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 3:38 [PATCH] mm/memcg: support control THP behaviour in cgroup cgel.zte
2022-05-05 12:49 ` kernel test robot
2022-05-05 13:31 ` kernel test robot
2022-05-05 16:09 ` kernel test robot [this message]
2022-05-06 13:41 ` Michal Hocko
2022-05-07 2:05 ` CGEL
2022-05-09 10:00 ` Michal Hocko
2022-05-09 11:26 ` CGEL
2022-05-09 11:48 ` Michal Hocko
2022-05-10 1:43 ` CGEL
2022-05-10 10:00 ` Michal Hocko
2022-05-10 11:52 ` CGEL
2022-05-10 13:36 ` Michal Hocko
2022-05-11 1:59 ` CGEL
2022-05-11 7:21 ` Michal Hocko
2022-05-11 9:47 ` CGEL
2022-05-18 5:58 ` CGEL
2022-05-10 19:34 ` Yang Shi
2022-05-11 2:19 ` CGEL
2022-05-11 2:47 ` Shakeel Butt
2022-05-11 3:11 ` Roman Gushchin
2022-05-11 3:31 ` CGEL
2022-05-18 8:14 ` Balbir Singh
2022-05-11 3:17 ` CGEL
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202205052327.RldmheYL-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cgel.zte@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=peterx@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=shy828301@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.org \
--cc=yang.yang29@zte.com.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).