From: kbuild test robot <fengguang.wu@intel.com>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 214/330] mm/memory-failure.c:1656: error: implicit declaration of function 'isolate_movable_page'
Date: Wed, 25 Jan 2017 16:05:33 +0800 [thread overview]
Message-ID: <201701251628.dBqAa7Kt%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: f7bc4a69dcfb1f03014b95e88b6a468f8cbf2d43
commit: 2cef0f79dcb7450917e324c8d26cdbe58097da31 [214/330] HWPOISON: soft offlining for non-lru movable pages
config: x86_64-randconfig-b0-01251455 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
git checkout 2cef0f79dcb7450917e324c8d26cdbe58097da31
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
mm/memory-failure.c: In function '__soft_offline_page':
>> mm/memory-failure.c:1656: error: implicit declaration of function 'isolate_movable_page'
vim +/isolate_movable_page +1656 mm/memory-failure.c
1650 * Try to migrate to a new page instead. migrate.c
1651 * handles a large number of cases for us.
1652 */
1653 if (PageLRU(page))
1654 ret = isolate_lru_page(page);
1655 else
> 1656 ret = !isolate_movable_page(page, ISOLATE_UNEVICTABLE);
1657 /*
1658 * Drop page reference which is came from get_any_page()
1659 * successful isolate_lru_page() already took another one.
---
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: 25023 bytes --]
next reply other threads:[~2017-01-25 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 8:05 kbuild test robot [this message]
2017-01-25 8:46 ` Yisheng Xie
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=201701251628.dBqAa7Kt%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=xieyisheng1@huawei.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