From: kbuild test robot <lkp@intel.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: kbuild-all@01.org, Jan Kara <jack@suse.cz>,
Amir Goldstein <amir73il@gmail.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Thelen <gthelen@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Mel Gorman <mgorman@suse.de>, Vlastimil Babka <vbabka@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] mm: memcg: plumbing memcg for kmalloc allocations
Date: Wed, 21 Feb 2018 07:38:11 +0800 [thread overview]
Message-ID: <201802210751.Zptrc19M%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180220194149.242009-3-shakeelb@google.com>
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
Hi Shakeel,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.16-rc2 next-20180220]
[cannot apply to linus/master]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Shakeel-Butt/Directed-kmem-charging/20180221-071026
base: git://git.cmpxchg.org/linux-mmotm.git master
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
arch/x86/events/core.o: In function `allocate_fake_cpuc':
>> core.c:(.text+0x52b): undefined reference to `__kmalloc_memcg'
arch/x86/events/core.o: In function `merge_attr':
>> core.c:(.init.text+0x2c): undefined reference to `__kmalloc_memcg'
arch/x86/events/intel/core.o: In function `intel_pmu_cpu_prepare':
core.c:(.text+0x1674): undefined reference to `__kmalloc_memcg'
arch/x86/events/intel/pt.o: In function `pt_init':
>> pt.c:(.init.text+0x125): undefined reference to `__kmalloc_memcg'
pt.c:(.init.text+0x13c): undefined reference to `__kmalloc_memcg'
arch/x86/kernel/e820.o:e820.c:(.init.text+0xa5b): more undefined references to `__kmalloc_memcg' follow
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6757 bytes --]
next prev parent reply other threads:[~2018-02-20 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 19:41 [PATCH 0/3] Directed kmem charging Shakeel Butt
2018-02-20 19:41 ` [PATCH 1/3] mm: memcg: plumbing memcg for kmem cache allocations Shakeel Butt
2018-02-20 19:41 ` [PATCH 2/3] mm: memcg: plumbing memcg for kmalloc allocations Shakeel Butt
2018-02-20 23:38 ` kbuild test robot [this message]
2018-02-21 0:50 ` kbuild test robot
2018-02-20 19:41 ` [PATCH 3/3] fs: fsnotify: account fsnotify metadata to kmemcg Shakeel Butt
2018-02-20 19:47 ` Shakeel Butt
2018-02-21 1:25 ` kbuild test robot
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=201802210751.Zptrc19M%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=cl@linux.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jack@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=shakeelb@google.com \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
/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).