From: kbuild test robot <fengguang.wu@intel.com>
To: Michal Hocko <mhocko@suse.com>
Cc: kbuild-all@01.org, linux-mm@kvack.org
Subject: [memcg:cleanups/kvmalloc 5/5] lib/rhashtable.c:80:31: error: 'gfp_' undeclared
Date: Sat, 7 Jan 2017 10:00:07 +0800 [thread overview]
Message-ID: <201701071003.45CZ1zD8%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1628 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git cleanups/kvmalloc
head: 351a752d1cd188fbe199f7a42094af72ee90fd63
commit: 351a752d1cd188fbe199f7a42094af72ee90fd63 [5/5] rhashtable: simplify a strange allocation pattern
config: xtensa-allyesconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.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
git checkout 351a752d1cd188fbe199f7a42094af72ee90fd63
# save the attached .config to linux build tree
make.cross ARCH=xtensa
All errors (new ones prefixed by >>):
lib/rhashtable.c: In function 'alloc_bucket_locks':
>> lib/rhashtable.c:80:31: error: 'gfp_' undeclared (first use in this function)
if (gfpflags_allow_blocking(gfp_))
^
lib/rhashtable.c:80:31: note: each undeclared identifier is reported only once for each function it appears in
vim +/gfp_ +80 lib/rhashtable.c
74 size = roundup_pow_of_two(nr_pcpus * ht->p.locks_mul);
75
76 /* Never allocate more than 0.5 locks per bucket */
77 size = min_t(unsigned int, size, tbl->size >> 1);
78
79 if (sizeof(spinlock_t) != 0) {
> 80 if (gfpflags_allow_blocking(gfp_))
81 tbl->locks = kvmalloc(size * sizeof(spinlock_t), gfp);
82 else
83 tbl->locks = kmalloc_array(size, sizeof(spinlock_t),
---
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: 48319 bytes --]
reply other threads:[~2017-01-07 2:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201701071003.45CZ1zD8%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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