From: kbuild test robot <lkp@intel.com>
To: Tahsin Erdogan <tahsin@google.com>
Cc: kbuild-all@01.org, Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Wilson <chris@chris-wilson.co.uk>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Roman Pen <r.peniaev@gmail.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Michal Hocko <mhocko@suse.com>, zijun_hu <zijun_hu@htc.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] percpu: improve allocation success rate for non-GFP_KERNEL callers
Date: Sun, 26 Feb 2017 08:48:04 +0800 [thread overview]
Message-ID: <201702260805.zhem8KFI%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170225210042.23678-1-tahsin@google.com>
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Hi Tahsin,
[auto build test ERROR on mmotm/master]
[also build test ERROR on v4.10 next-20170224]
[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/Tahsin-Erdogan/percpu-remove-unused-chunk_alloc-parameter-from-pcpu_get_pages/20170226-052515
base: git://git.cmpxchg.org/linux-mmotm.git master
config: blackfin-BF561-EZKIT-SMP_defconfig (attached as .config)
compiler: bfin-uclinux-gcc (GCC) 6.2.0
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=blackfin
All errors (new ones prefixed by >>):
mm/built-in.o: In function `pcpu_mem_zalloc':
>> mm/percpu.c:314: undefined reference to `vmalloc_gfp'
vim +314 mm/percpu.c
308 if (WARN_ON_ONCE(!slab_is_available()))
309 return NULL;
310
311 if (size <= PAGE_SIZE)
312 return kzalloc(size, gfp);
313 else
> 314 return vmalloc_gfp(size, gfp | __GFP_HIGHMEM | __GFP_ZERO);
315 }
316
317 /**
---
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: 10736 bytes --]
next prev parent reply other threads:[~2017-02-26 0:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 21:00 Tahsin Erdogan
2017-02-25 23:54 ` kbuild test robot
2017-02-26 0:48 ` kbuild test robot [this message]
2017-02-26 4:38 ` [PATCH v2 " Tahsin Erdogan
2017-02-27 9:52 ` Michal Hocko
2017-02-27 13:00 ` Tahsin Erdogan
2017-02-27 15:25 ` Michal Hocko
2017-02-27 17:01 ` Tahsin Erdogan
2017-02-27 17:07 ` Michal Hocko
2017-02-27 17:14 ` Michal Hocko
2017-02-27 19:32 ` Tahsin Erdogan
2017-02-27 19:47 ` Michal Hocko
2017-02-27 19:51 ` Tejun Heo
2017-02-27 20:27 ` Tahsin Erdogan
2017-02-27 20:29 ` Tejun Heo
2017-02-27 20:37 ` Tahsin Erdogan
2017-02-27 20:45 ` Tejun Heo
2017-02-27 21:12 ` Tahsin Erdogan
2017-02-27 21:28 ` Tejun Heo
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=201702260805.zhem8KFI%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=chris@chris-wilson.co.uk \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=r.peniaev@gmail.com \
--cc=tahsin@google.com \
--cc=tj@kernel.org \
--cc=zijun_hu@htc.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