From: kbuild test robot <lkp@intel.com>
To: David Rientjes <rientjes@google.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [patch -mm] mm, vmalloc: remove VM_VPAGES
Date: Thu, 19 Nov 2015 08:39:32 +0800 [thread overview]
Message-ID: <201511190854.Z8lkE4h1%fengguang.wu@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1511181629220.1381@chino.kir.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 1745 bytes --]
Hi David,
[auto build test ERROR on: next-20151118]
[also build test ERROR on: v4.4-rc1]
url: https://github.com/0day-ci/linux/commits/David-Rientjes/mm-vmalloc-remove-VM_VPAGES/20151119-083326
config: i386-tinyconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
mm/vmalloc.c: In function '__vunmap':
>> mm/vmalloc.c:1484:21: error: 'VM_VPAGES' undeclared (first use in this function)
if (area->flags & VM_VPAGES)
^
mm/vmalloc.c:1484:21: note: each undeclared identifier is reported only once for each function it appears in
vim +/VM_VPAGES +1484 mm/vmalloc.c
bf53d6f8 Christoph Lameter 2008-02-04 1478 struct page *page = area->pages[i];
bf53d6f8 Christoph Lameter 2008-02-04 1479
bf53d6f8 Christoph Lameter 2008-02-04 1480 BUG_ON(!page);
bf53d6f8 Christoph Lameter 2008-02-04 1481 __free_page(page);
^1da177e Linus Torvalds 2005-04-16 1482 }
^1da177e Linus Torvalds 2005-04-16 1483
8757d5fa Jan Kiszka 2006-07-14 @1484 if (area->flags & VM_VPAGES)
^1da177e Linus Torvalds 2005-04-16 1485 vfree(area->pages);
^1da177e Linus Torvalds 2005-04-16 1486 else
^1da177e Linus Torvalds 2005-04-16 1487 kfree(area->pages);
:::::: The code at line 1484 was first introduced by commit
:::::: 8757d5fa6b75e8ea906baf0309d49b980e7f9bc9 [PATCH] mm: fix oom roll-back of __vmalloc_area_node
:::::: TO: Jan Kiszka <jan.kiszka@web.de>
:::::: CC: Linus Torvalds <torvalds@g5.osdl.org>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6113 bytes --]
next prev parent reply other threads:[~2015-11-19 0:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 0:30 David Rientjes
2015-11-19 0:39 ` kbuild test robot [this message]
2015-11-19 1:00 ` David Rientjes
2015-11-19 11:33 ` [kbuild-all] " Fengguang Wu
2015-11-19 12:23 ` Tetsuo Handa
2015-11-19 12:35 ` Fengguang Wu
2015-11-19 18:37 ` Johannes Weiner
2015-11-20 1:46 ` Fengguang Wu
2015-11-19 0:40 ` 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=201511190854.Z8lkE4h1%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rientjes@google.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
all inboxes | Powered by JetHome®