From: kbuild test robot <fengguang.wu@intel.com>
To: Roman Gushchin <guro@fb.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 123/250] fs/dcache.c:278:22: error: implicit declaration of function 'kmalloc_index'; did you mean 'kmalloc_node'?
Date: Thu, 8 Mar 2018 10:33:32 +0800 [thread overview]
Message-ID: <201803081029.PeTMgTCE%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 37ec9d8b887635603a859a06aa0406342b1068d8
commit: 364404b4416a52a9991414b2183f85afb42a5fe8 [123/250] dcache: account external names as indirectly reclaimable memory
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 364404b4416a52a9991414b2183f85afb42a5fe8
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs/dcache.c: In function '__d_free_external':
>> fs/dcache.c:278:22: error: implicit declaration of function 'kmalloc_index'; did you mean 'kmalloc_node'? [-Werror=implicit-function-declaration]
-kmalloc_size(kmalloc_index(bytes)));
^~~~~~~~~~~~~
kmalloc_node
cc1: some warnings being treated as errors
vim +278 fs/dcache.c
268
269 static void __d_free_external(struct rcu_head *head)
270 {
271 struct dentry *dentry = container_of(head, struct dentry, d_u.d_rcu);
272 struct external_name *name = external_name(dentry);
273 unsigned long bytes;
274
275 bytes = dentry->d_name.len + offsetof(struct external_name, name[1]);
276 mod_node_page_state(page_pgdat(virt_to_page(name)),
277 NR_INDIRECTLY_RECLAIMABLE_BYTES,
> 278 -kmalloc_size(kmalloc_index(bytes)));
279
280 kfree(name);
281 kmem_cache_free(dentry_cache, dentry);
282 }
283
---
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: 6744 bytes --]
reply other threads:[~2018-03-08 2:33 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=201803081029.PeTMgTCE%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
/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).